Controller for maintaining user information in a group communication network

ABSTRACT

A method and apparatus for maintaining information for users of push-to-talk communication devices in a group communication network provides for maintaining information about a net in the group communication network and maintaining information about a user in the net.

CROSS-REFERENCE TO RELATED APPLICATION

[0001] This application is a division of U.S. patent application Ser.No. 09/518,776, filed Mar. 3, 2000, pending, which application isincorporated herein by reference in its entirety.

FEDERAL RESEARCH STATEMENT

[0002] The U.S. Government has a paid-up license in this invention andthe right in limited circumstances to require the patent owner tolicense others on reasonable terms as provided by the terms ofMDA904-96-G-0035 awarded by the National Security Agency.

BACKGROUND OF THE INVENTION

[0003] I. Field of the Invention

[0004] The present invention relates to point to multi-pointcommunications systems. More specifically, the present invention relatesto an apparatus and method for maintaining information about a net aswell as information about the users in the net in a group communicationnetwork.

[0005] II. Description of the Related Art

[0006] Point-to-multipoint communication systems have been used toprovide communications generally between a central location and multipleusers of the system. For example, dispatch systems using Land MobileRadios (LMRs) have been used in trucks, taxis, buses, and other vehiclesin order to communicate scheduling information between a centraldispatch center and one or more corresponding fleet vehicles.Communications may be directed at a specific vehicle in the fleet or toall vehicles simultaneously.

[0007] Another example of a point-to-multipoint communication system isa wireless push-to-talk system. Such a system allows a group ofindividuals, each having a wireless communication device, to communicatewith other members of the group. Typically, a push-to-talk system relieson a single frequency, or dedicated channel, over which communicationsare received by the wireless communication devices. In most systems,only one member may transmit information to the other members at a time.However, all members can listen to the dedicated broadcast channel toreceive communications from the single member who is transmitting.Members desiring to transmit to other members of the system typicallysends an access request by depressing a push-to-talk button on theirrespective communication device that allows the user sole access to thededicated channel.

[0008] Push-to-talk systems are typically used in outdoor settings wherea group of people, or members, require communications with each other ina “point-to-multipoint” fashion. Examples of push-to-talk system usesinclude workgroup communications, security communications, constructionsite communication, and localized military communications. The group ofpeople requiring communications with each other is commonly known as a“net,” each member of the net sometimes referred to as a “net member.”

[0009] In a typical push-to-talk system, a dedicated channel, sometimesreferred to as a broadcast channel, is used to transmit communicationsfrom one member to multiple other members of the net simultaneously. Thededicated channel may comprise a single channel or frequency, or a groupof individual channels managed by a controller to imitate the singlechannel. In either case, only one member may transmit voice and/or datacommunications to the other member users at any given time. If anothermember attempts to transmit over the broadcast channel while anothermember is transmitting, interference between the two competingcommunications will occur, resulting in non-intelligible communicationsbeing received by the other net members.

SUMMARY OF THE INVENTION

[0010] The disclosed embodiments provide a novel and improved method andapparatus for maintaining user information in a group communicationnetwork. In one aspect of the invention, a method for maintaininginformation about users of push-to-talk communication devices in a groupcommunication network includes the steps of maintaining informationabout the a in the group communication network and maintaininginformation about a user in the net.

[0011] In another aspect of the invention, a database for maintaininguser information in a group communication network includes a firstportion for maintaining information about a net in the groupcommunication network and a second portion for maintaining informationabout a user in the net.

[0012] In another aspect of the invention, a controller for maintaininguser information in a group communication network includes a memory unitand a processor communicatively coupled with the memory unit. Theprocessor is capable of maintaining information about a net in the groupcommunication network and maintaining information about a user in thenet. In one aspect, the communication devices include a push-to-talk(PTT) device.

BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The features and advantages of the present invention will becomemore apparent from the detailed description set forth below when takenin conjunction with the drawings in which like reference charactersidentify correspondingly throughout and wherein:

[0014]FIG. 1 illustrates a net broadcast system.

[0015]FIG. 2 illustrates a NBS net and how communication devicesinteract with a communications manager (CM) 104.

[0016]FIG. 3 illustrates a functional block diagram of the CM.

[0017]FIG. 4 illustrates an example of a NBS SIP signaling protocolstack.

[0018]FIG. 5 illustrates an NBS media signaling protocol stack.

[0019]FIG. 6 illustrates real time protocol voice media protocol stack.

[0020]FIG. 7 illustrates a UDP voice media protocol stack.

[0021]FIG. 8 illustrates a media traffic protocol stack.

[0022]FIG. 9 illustrates a DNS client protocol stack.

[0023]FIG. 10 illustrates the high level functionality of the groupservices module 500 of the CD.

[0024]FIG. 11 illustrates SIP call signaling 350.

[0025]FIG. 12 illustrates a media signaling message sequence.

[0026]FIG. 13 illustrates the sequence of media signaling messages withrespect to dormancy.

[0027]FIG. 14 illustrates a sequence of NBS media signaling messages.

[0028]FIG. 15 illustrates a state diagram of the CM 104.

[0029]FIG. 16 illustrates a state diagram of the CD 352.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0030] The net broadcast service (NBS) system enables Internet Protocol(IP) communication devices to participate in a group voice and dataconference. NBS is primarily a Voice over IP (VoIP) application. Voicecommunication is transmitted from a talker endpoint communication deviceto one or more listeners by encapsulating voice frames in IP datagrams.Data with voice may also be transmitted in this manner. The NBS systemis described in U.S. patent application Ser. No. 09/518,622, filed Mar.3, 2000 and U.S. patent application Ser. No. 09/518,985, filed Mar. 3,2000, and are specifically incorporated by reference herein.

[0031]FIG. 1 illustrates a functional block diagram of a groupcommunication system 10. The group communication system 10 is also knownas a push-to-talk system, a net broadcast service (NBS), a dispatchsystem, or a point-to-multi-point communication system. A definingcharacteristic of such the NBS system is that, generally, only one usermay transmit information to other users at any given time. In the NBS10, a group of communication device users, individually known as netmembers, communicate with one another using a communication deviceassigned to each net member.

[0032] The term “net” denotes a group of communication device usersauthorized to communicate with each other. Generally, a central databasecontains information identifying the members of each particular net.More than one net may operate in the same communication system. Forinstance, a first net may be defined having ten members and a second netmay be defined, having twenty members. The ten members of the first netcan communicate with each other, but generally not to members of thesecond net. In other situations, members of different nets are able tomonitor communications between members of more than one net, but areonly able to transmit information to members within their own net.

[0033] The net operates over an existing communications system, withoutrequiring substantial changes to the existing infrastructure. Thus, acontroller and users on a net may operate in any system capable oftransmitting and receiving packet information using Internet Protocol(IP), such as a Code Division Multiple Access (CDMA) system, a TimeDivision Multiple Access (TDMA) system, a Global System for MobileCommunications (GSM) system, satellite communication systems such asGlobalstar™ or Iradium™, or a variety of other systems.

[0034] Net members communicate with each other using an assignedcommunication device, shown as communication devices (CD) 12, 14, 16 and17. CDs 12, 14, 16 and 17 may be wireline or wireless communicationdevices such as terrestrial wireless telephones, wireline telephoneshaving push-to-talk capability, satellite telephones equipped withpush-to-talk functionality, wireless video cameras, still cameras, audiodevices such as music recorders or players, laptop or desktop computers,paging devices, or any combination thereof. For example, the CD 12 maycomprise a wireless terrestrial telephone having a video camera anddisplay. Furthermore, each CD may be able to send and receiveinformation in either a secure mode, or a non-secure (clear) mode.Throughout the following discussion, reference to an individual CD maybe expressed by a wireless push-to-talk phone. However, it should beunderstood that reference to a CD is not intended to be limited as such,and may encompass other communication devices that have the capabilityto transmit and receive packet information in accordance with InternetProtocol (IP).

[0035] In the NBS system 100 of FIG. 2, a transmission privilege isdefined that generally allows a single user to transmit information toother net members at any given time. The transmission privilege isgranted or denied to requesting net members, depending on whether or notthe transmission privilege is currently assigned to another net memberwhen the request is received. The process of granting and denyingtransmission requests is known as arbitration. Other arbitration schemesevaluate factors such as priority levels assigned to each CD indetermining whether a requesting net member is granted the transmissionprivilege.

[0036] In order to participate in the NBS system 10, CDs 12, 14, 16, and17 each have the ability to request transmission privilege from acontroller or a communications manager (CM) 18. CM 18 generally managesthe real-time and administrative operation of nets. The CM is any typeof computer type device having at least one processor and memory. In anembodiment, the CM is a Sun Workstation Netra T1™.

[0037] The CM 18 maintains a list of defined nets, defined as eitherclear or secure. Transitions between clear and secure are generally notpermitted. A secure net relies on encryption provided by the individualCDs to provide authentication and guard against eavesdropping.Encryption for secure nets is implemented on an end-to-end basis,meaning that encryption and decryption takes place within each CD. TheCM 18 generally operates without knowledge of security algorithms, keys,or policies.

[0038] The CM 18 manages remotely through either a communication systemservice provider, net members, or both, assuming that authorization isprovided by the service provider. The CM 18 may receive net definitionsthrough an external administration interface. Net members may requestadministrative actions through their service provider or administratenet functions through defined systems, such as a member-operatedsecurity manager (SM) 20 that conforms to a CM 18 administrationinterface. The CM 18 can authenticate to high-grade commercial standardsany party attempting to establish or modify a net.

[0039] The SM 20 is an optional component of the NBS system 10 thatperforms key management, user authentication, and related tasks tosupport secure nets. A single group communication system may interactwith one or more SM 20. The SM 20 is generally not involved in thereal-time control of a net, including net activation or PTT arbitration.The SM 20 may have administration capabilities compatible with a CM 18interface to automate administration functions. The SM 20 may also becapable of acting as a data endpoint for the purpose of participating ina net, broadcast net keys, or simply monitor net traffic.

[0040] In one embodiment, the means for requesting the transmissionprivilege from a CD comprises a push-to-talk (PTT) key or switch. When auser in the NBS 10 desires to transmit information to other net members,the push-to-talk switch located on his or her CD is depressed, sending arequest to obtain the transmission privilege from the CM 18. If no othernet member is currently assigned the transmission privilege, therequesting user is granted the transmission privilege and is notified byan audible, visual, or tactile alert through the CD. After therequesting user has been granted the transmission privilege, informationmay be then transmitted from that user to the other net member.

[0041] In one embodiment of the present invention, each wireless netmember establishes a forward link and a reverse link with one or morebase stations 22 or a satellite gateway 24, as the case may be. The basestation 22 is used to describe a communication channel from the basestation 22 or the satellite gateway 24 to a CD. The satellite gateway 24is used to describe a communication channel from a CD to a base station22 or gateway 24. Voice and/or data is converted into data packets usinga CD, the data packets suitable for a particular distributed network 26through which communications to other users take place. In oneembodiment, distributed network 26 is the Internet. In anotherembodiment, a dedicated forward channel is established in eachcommunication system (i.e., a terrestrial communication system and asatellite communication system) for broadcasting information from eachnet member to the other net members. Each net member receivescommunications from other net members over the dedicated channel. In yetanother embodiment, a dedicated reverse link is established in eachcommunication system for transmitting information to the CM 18. Finally,a combination of the above schemes may be used. For instance, a schememay be establishing a dedicated forward broadcast channel but requiringwireless CDs to transmit information to the CM 18 over an individualreverse link assigned to each CD.

[0042] When a first net member wishes to transmit information to othermembers of the net, the first net member requests the transmissionprivilege by pressing a push-to-talk key on his or her CD, whichgenerates a request formatted for transmission over the distributednetwork 26. In the case of CDs 12, 14 and 16, the request is transmittedover-the-air to one or more base stations 22. A mobile switching center(MSC) 28 comprises a well-known inter-working function (IWF) forprocessing data packets, including the request, between the MSC 28 andthe distributed network 26. For CD 16, the request is transmitted viasatellite to satellite gateway 24. For the CD 17, the request istransmitted to the Public Switched Telephone Network (PSTN) 30, then toa modem bank 32. Modem bank 32 receives the request and provides it tothe distributed network 26. A NBS terminal 34 monitors traffic of theNBS system through its connection to the Internet 26. Since the NBSterminal 34 is connected to the Internet 26, geographic proximity to netparticipants is not necessary.

[0043] If no other member currently holds the transmission privilegewhen the transmission privilege request is received by CM 18, CM 18transmits a message to the requesting net member, notifying it that thetransmission privilege has been granted. Audio, visual, or otherinformation from the first net member may then be transmitted to theother net members by sending the information to CM 18, using one of thejust-described transmission paths. In one embodiment, CM 18 thenprovides the information to the net members by duplicating theinformation and sending each duplicate to the net members. If a singlebroadcast channel is used, the information need only be duplicated oncefor each broadcast channel in use.

[0044] In an alternative embodiment, CM 18 is incorporated into MSC 28so that data packets from supporting base stations are routed directlyto CM 18 without being routed onto distributed network 26. In thisembodiment, CM 18 is still connected to distributed network 26 so thatother communication systems and devices can participate in a groupcommunication.

[0045] CM 18 maintains one or more databases for managing informationpertaining to individual net members as well as to each defined net. Forexample, for each net member, a database may comprise information suchas the user name, account number, a telephone number, or dial number,associated with the member's CD, a Mobile Identification Number assignedto the CD, the current member's status in the net, such as whether themember is actively participating in the net, a priority code fordetermining how the transmission privilege is assigned, a data telephonenumber associated with the CD, an IP address associated with the CD, andan indication of which nets the member is authorized to communicate.Other related types of information may also be stored by the databasewith respect to each net member.

[0046] As part of the NBS infrastructure, the communications manager(CM) forms connections of individual communication terminals to form onetalk group, or net. The CM comprises a variety of functionalcapabilities in hardware and software that are configurable in differentways to accommodate different applications. Generally, the CM providescapability to manage realtime, administrative, and authenticityoperations of (NBS) nets, push-to-talk (PTT) request arbitration,maintenance and distribution of net membership and registration lists,call set-up and tear-down of necessary CDMA system and networkresources, as well as overall control of net status.

[0047] The NBS net may be within a stand-alone deployable cellularsystem, or a large multiple site configuration. In the case of a largeconfiguration, multiple CMs may be deployed geographically to form asingle, integrated system, each operates as a plug-in module intoexisting cellular infrastructure. As such, new features introduced byNBS nets are available to cellular users without requiring modificationto existing cellular infrastructure.

[0048] A function of the CM is to maintain a list of defined NBS nets.Each net definition includes a net identifier, a list of members,including phone numbers or other identifying information, user priorityinformation, and other generic administration information. Nets arestatically defined as either clear or secure, and transitions betweenclear and secure are not permitted. A secure NBS net typically usesmedia encryption to provide authentication and guard againsteavesdropping. Media encryption for secure nets is implemented on anend-to-end basis, meaning encryption and decryption takes place withinthe communication device. The CM operates without knowledge of securityalgorithms, keys, or policies.

[0049] The CM receives net definitions through an externaladministration interface. Customers may request administrative actionsthrough its service provider or administrate net functions throughdefined systems, such as a customer-operated security manager thatconforms to the CM administration interface. The CM authenticates tohigh-grade commercial standards for any party attempting to establish ormodify a net.

[0050] Before one embodiment of the invention is explained in detail, itis to be understood that the invention is not limited in its applicationto the details of the construction and the arrangement of the componentsset forth in the following description or illustrated in the drawings.The invention is capable of other embodiments and are carried out invarious ways. Also, it is understood that the phraseology andterminology used herein is for purpose of description and should not beregarded as limiting.

[0051]FIG. 2 illustrates a NBS net 100 and how communication devicesinteract with a CM 104. Multiple CMs 104 may be deployed as desired forlarge-scale NBS nets 100. In FIG. 2, communication device 108, or a CD108, has permission to transmit media onto the net. In this case, the CD108 is known as the talker, and transmits media over a channel. When theCD 108 is designated as the talker, the remaining net participants,communication devices 112 and 116 (or CD 112 and CD 116) do not havepermission to transmit media to the net. Accordingly, CD 112 and CD 116are designated as listeners. If CD 116 is designated as the talker, CD108 and CD 112 are designated as listeners, and so on.

[0052] As described above, each CD 108, 112 and 116 is connected to theCM 104 using at least one channel. In an embodiment, the channel isdivided into separate channels comprising a session initiation protocol(SIP) channel 120, a NBS media signaling channel 124, and a mediatraffic channel 128. The session initiation protocol (SIP) channel 120and the NBS media signaling channel 124 may be used at any time asbandwidth allows, regardless of being designated a talker or a listener,by any of the CD's 108, 112 and 116. The SIP is an Internet EngineeringTask Force (IETF) defined application-layer protocol that describescontrol mechanisms to establish, modify, and terminate multimediasessions operating over Internet Protocol (IP). SIP provides a generalsolution to call-signaling problems for Internet telephony applicationsby supporting means to register and locate users, mechanism that defineuser capabilities and describe media parameters, mechanisms to determineuser availability, call setup, and call-handling.

[0053] The SIP channel 120 is used to start and end participation of aCD within the net 100. Optionally, a session description protocol (SDP)signal may also be used within the SIP channel 120. When the CD'sparticipation within an NBS net is setup using the SIP channel 120,real-time call control and signaling between the CD and the CM 104 takesplace using the NBS media signaling channel 124. Specifically, amongother tasks, the NBS media signaling channel 124 is used for handlingpush-to-talk requests and releases, arbitrate between conflictingrequests, or floor control, announce the beginning and end ofinformation transmission, manage net dormancy, track endpointconnectivity, request and exchange net status, notification and errormessages. The protocol of the NBS media signaling channel 124 minimizesthe length of the most common messages, and to simplify the task ofinterpreting replies and responding to requests while retainingflexibility for future enhancements. The protocol of the NBS mediasignaling channel 124 also allows requests to be resent withoutadversely affecting protocol state.

[0054] Signaling traffic on the media channel 124 may further bedifferentiated into two categories: call setup and control signaling,which consists primarily of SIP invitation requests andacknowledgements, and media signaling, which is comprised primarily ofreal-time floor control requests and related asynchronous messages.Media traffic on the media traffic channel 128 is comprised of real-timepoint-to-multi-point voice and/or data broadcasts. Both messagingcategories have unique functional attributes. In addition, each CD mayissue Domain Name Service (DNS) client requests to facilitate mappingfully-qualified DNS hostnames to Internet network addresses.

[0055] NBS call setup and call control signaling is performed accordingto SIP semantics. Although SIP may be transported using either the wellknown User Datagram Protocol (UDP) or Transmission Control Protocol(TCP), in a preferred embodiment, each CD performs SIP based signalingfunctions using UDP, as illustrated in FIG. 4. Also, each CM expects toreceive all SIP signaling requests via UDP. Real-time signaling occursvia dynamic UDP/IP interfaces on the CM and each CD. Other signaling maytake place via a fixed TCP/IP interface between the CM and the CD usingthe SIP.

[0056]FIG. 3 illustrates the modules and physical make-up of the CM 200.The CM 200 comprises of a CM core module or complex 204, at least onenet module, or media control unit (MCU) 208 and 212, a DNS server 216, aredirect server 220 and an administration workstation 224. The CM corecomplex 204 provides administration capability to a Java™-capableweb-browser. One or more DNS servers 216 may also be included in the CMcore complex 204. The CM core complex 204 further comprises a CM node228 and a database server 232. The CM 200 is separable into at least twoparts, the CM core complex 204 and each MCU node 208. After initialconnection into the CM core complex 204, a net is operated by MCU node208. The MCU node 208 sends and receives information as necessary fromthe CM core complex 204. The separability of the CM core complex 204allows for versatility in that once a particular net is established, thenet is operated by a dedicated MCU node 208. This allows CM core complex204 to provide initial connections with other potential nets,irrespective of the type of communication structure in which the netwishes to operate. Also, the CM core complex 204 may be geographicallydisplaced from the MCU node 208. For example, a single CM core complex204 may be located in the central part of the United States, and aplurality of MCU nodes 208 may be located regionally to operate netsfrom its given region. As such, the CM core complex 204 may route a userto a particular MCU node 208 based on the location of the user. Also,information may be provided to a user or group of users based onlocation, such as location-based broadcasting, directions, oridentification of landmarks.

[0057] The CM node 228 provides centralized functionality associatedwith NBS nets. The CM node 228 comprises a session initiation protocoluser agent server (SIP UAS) server 236, and CM manager 240, a centralbilling log 244, and an administration server 248. The SIP UAS server236 supports user requests for net lists and handles SIP invite messagesfor nets. When a SIP invite message is received from a communicationdevice, the net assigns the communication device to an appropriate MCUnode 208, and directs the communication device to the MCU node 208.

[0058] The CM manager 240 monitors the status of all the MCU nodeswithin a net, and assigns the execution of nets to given MCU nodes, suchas the MCU node 208. The CM manager 240 handles administrative functionspertaining to net administration, including the creation and deletion ofnets, defining new and deleting existing users, adding and removingusers as net members, and adjusting various operating parameters at auser, net, or CM wide basis.

[0059] The central billing log 244 maintains time and identificationinformation for billing purposes. The central billing log receivesbilling log information from a local log server 260 of the MCU node 208.Detailed log information of each user, such as which communicationdevices are active on the net, for how long, from where, and when andfor how long each CD is a talker or a listener, is maintained. TheAdministration Server 248 supports an interface to allow theAdministration workstation 224 to retrieve status information, initiatedatabase administration and system management functions through the netstatus interface.

[0060] The CM implements both the SIP user-agent server 236 and a SIPMCU server 252. To support NBS, each CD implements a SIP user-agentclient. The CM receives incoming SIP connections on an advertised node,or port. When a connection occurs, the SIP server 236 receives andprocesses requests according to SIP call-signaling conventions. The SIPserver 236 is capable of processing multiple call-signaling connectionsin parallel.

[0061] To conserve network resources, the CD may release its UDPconnection with the SIP server 236 after it has successfully (orunsuccessfully) joined the NBS net 100. The UDP connection may bereinstated later to send additional SIP call-signaling requests (forexample, to leave the net or switch to another net).

[0062]FIG. 4 illustrates an example of a NBS SIP signaling protocolstack 300. The stack is a collection of protocol layers that implementsnetwork communication. The protocol associated with each layercommunicates with the layers immediately above and below it, and assumesthe support of underlying layers. Because UDP is a less reliableconnectionless transport, application level reliability is preferable toinsure robust communication, which is achieved by implementing by SIPcompliant endpoints. Generally, SIP call-signaling 302 on UDP streams304 are encapsulated within IP protocol 306. No special formatting isrequired. SIP call-signaling IP packets 306 are exchanged between, forexample, a CDMA cellular based CD or a dial-up PSTN based CD, which areencapsulated within point-to-point protocol (PPP) frames 308.Accordingly, no special formatting is required. Also, SIP call-signalingPPP frames 308 exchanged between a CDMA cellular based CD and a basestation are encapsulated within a radio link protocol (RLP) 310. Fordial-up PSTN based users, an appropriate modem standard, such as V.32bisor V.90, may replace RLP 310. In either case, special treatment isgenerally not required and an error-free physical link is not assumed.

[0063]FIG. 5 illustrates an NBS media signaling protocol stack 312,transporting voice and data traffic using UDP datagrams 304 over IP 306.NBS media signaling 314 is layered onto UDP/IP traffic, and is handledin a similar manner with respect to the description of FIG. 4.

[0064]FIG. 6 illustrates a real-time voice-media protocol stack 320. Inthis embodiment, vocoder payload data 322 is layered on real timeprotocol (RTP) 324. RTP 324 is then layered onto UDP 304 and IP 306. Inan optional embodiment, compressed real time protocol (CRTP) headercompression 330 is used to further encapsulate media traffic using RTP324 at the application layer. Header compression techniques may beapplied as appropriate to all UDP/IP incoming and outgoing UDP/IPtraffic illustrated in FIGS. 4 9. Media signaling requests and responsesare encapsulated within UDP datagrams. When available, CRTP headercompression may be applied to reduce the impact of sending uncompressedUDP/IP headers. In FIG. 6, CRTP compresses RTP layer 324, UDP layer 304,IP layer 306 and the PPP layer 308. In FIGS. 4, 5 and 7-9, CRTP 320compresses the layers between and including UDP 304 to PPP 308.

[0065] In operation, each CD dynamically selects a UDP port on which itintends to listen for NBS media signaling requests and communicates theport number to the SIP server 236 as part of the SIP invitation itdelivers when attempting to join a net. The net's CM media signalingdestination address (including the UDP port number) is described in thenet's session description delivered as part of a successful SIP INVITErequest's response to the CD. Unlike SIP signaling addresses, mediasignaling destination addresses are net specific and may change betweeninstances of a CD joining a net. Multiple nets hosted by the same CMgenerally operate independently and do not share media signaling ormedia traffic ports. However, it is contemplated that multiple nets mayshare media signaling and media traffic ports.

[0066] Referring to FIG. 6, voice traffic is encapsulated by groupingone or more vocoder frames within an RTP/UDP 324 or UDP payload 304. Theuse of RTP 324 with CRTP 330 enabled is used to minimize end-to-endmedia latency and provide interoperability with IP telephonyapplications and services. In either case, the CD dynamically selectsthe UDP port on which it expects to receive media traffic andcommunicates the port number to the SIP server 236 as part of the SIPinvitation it delivers when attempting to join a net.

[0067] The net's vocoder and transport encapsulation protocol, as wellas its media traffic destination address (including the UDP portnumber), is described in the session description response to asuccessful SIP invitation request from the SIP server 236. Like a net'smedia signaling addresses, the media traffic destination addresses arenet specific and may change between instances of a CD joining a net.

[0068] Typically, as shown in FIG. 6, voice traffic is encapsulated atthe application layer using RTP 324, which segments each UDP datagram304 into a RTP header 324 and vocoder payload 322. FIG. 7 illustrates aUDP voice media protocol stack 332. Voice traffic may optionally beencapsulated purely using UDP datagrams 304, with no RTP encapsulation,typically when CRTP header compression 330 is unavailable or unsupportedby a net member. FIG. 8 illustrates a media traffic protocol stack 334.The media traffic protocol stack 334 is used for net participants withno application-level RTP encapsulation. Data 336 is encapsulated intoUDP datagrams 304.

[0069] The structure of the UDP payload 304 follows the definition givenfor a corresponding RTP payload 324, without the RTP header fields. Thedecision to encapsulate media directly into UDP 304 is configured by thenet's administrator 248 and advertised by the net's sessionannouncement. In addition to voice media, NBS nets may also supportarbitrary data broadcasts. If a net supports a data broadcast channel,the SIP server 236 advertises the media type in the net's SIP sessiondescription when a CD formally joins the net.

[0070]FIG. 9 illustrates a DNS client protocol stack 338. Each CDincludes the capability to resolve Internet domain names into Internetaddresses using a Domain Name Service (DNS) protocol 340. The CDoperates as a DNS client. The CD encapsulates DNS 340 requests using UDP304, as shown in FIG. 9. In order for the CD to resolve DNS hostnames,the CD is provisioned with the IP network address of the DNS server 216,as shown in FIG. 3. The DNS address is also configurable by the CDservice provider and, optionally, by the user.

[0071] In addition to voice media, nets may also support arbitrary databroadcasts, such as secure net rekey, email, data files, etc. If a netsupports a data broadcast channel, the CM advertises the media type inthe net's SIP session description when the CD formally joins the net.Like traditional media broadcasts, generic data broadcasts operate overRLP in one embodiment (or a corresponding physical layer) but aregenerally considered less reliable transports.

[0072] The CD includes the capability to resolve Internet domain namesinto Internet addresses using the Domain Name Service (DNS) protocol, asdefined in RFC 1034. Alternatively, the CD operates as a DNS client orresolver, as described in RFC 1035.

[0073] In order for the CD to resolve DNS hostnames, the CD ispreprogrammed with the IP network address of a DNS server. The DNSaddress is also configurable by the CD service provider and, optionally,by the user.

[0074] The CM 104 may optionally be configured to act as a DNS server216. Although it may respond to DNS requests from foreign entities usingTCP as the transport protocol, for the purpose of servicing requestsoriginating with the CD, the SIP server 236 also encapsulates DNSmessages using the UDP 304 according to FIG. 8.

[0075] The NBS also takes advantage of the development of a cellularmulticast channel. Such a channel generically allows one transmittingstation to address N listening stations directly over one forwardchannel, without the need for N separate rebroadcasts of the transmitteddata. The presence of a cellular multicast channel implies changes tothe NBS media stack primarily below the IP network layer. To takeadvantage of the efficiencies provided by a cellular multicast channel,a net's media signaling and traffic destination addresses areconventional IP multicast channels, and CM originated media signalingand traffic broadcasts are multicast broadcasts. Each CD originatedmedia signaling and traffic broadcasts and SIP signaling remain aspoint-to-point communications.

[0076] The Radio Link Protocol (RLP) 310 shown in FIGS. 4-9 may bemodified within each CD to minimize the latency experienced whenlink-layer (RLP frame) loss occurs. Such modifications are optional anddo not necessarily affect the operation of transport of applicationlayer protocols, since neither TCP nor UDP 304 assumes a reliablenetwork (IP) or link-layer service.

[0077] A variety of the RLP 310 modification strategies are possible.For example, the RLP 310 may be modified to send multiple messages, suchas NAK responses, after an initial RLP timeout, thus prompting theremote end to transmit multiple copies of the lost RLP 310 frame andimproving the chances of a successful the RLP 310 recovery. The RLP 310may also be modified to never send a NAK responses (after the RLPtimeout expires) and allow dropped RLP 310 frames to force higher levelsof the protocol stack to generate errors. Any application levelprotocols based on TCP recover routinely using TCP's error recoverymechanisms. Traffic relying on the UDP 304 for transport alreadycontends with the potential for loss.

[0078] Referring back to FIG. 2, once the CD establishes participationwithin the NBS net 100 using the SIP channel 120, the CD is prepared tosend and receive media from the net 100 on a specific media port of theCD over the media traffic channel 128. If the CD gains control of thefloor through media signaling, as the case with CD 108 of FIG. 2, the CDtransmits media to the destination network and transport addresses asindicated in the session description of the net 100. The CD decodesmedia received on its media ports according to the vocoder and mediaformat defined in the session description of the net 100 received in aninvite response when the CD joined the net 100. The CD codes andencapsulates media sent to the net 100 according to the vocoder andmedia format defined in the session description of the net 100 receivedin an invite response when the CD joined the net 100.

[0079] Each CD participating in a net determines the destination networkand transport address for each media channel from the sessiondescription received from the SIP server 236 of the CM 104 andacknowledged during the SIP call set-up and use it to addresscorresponding media sent within the net 100. Each CD provides a packetdata connection to the CM. Changes in the CD implementation of thisinterface may be made to optimize NBS performance. Changes to theinfrastructure side of this interface are generally not necessary. TheCD may optionally support most NBS activities using Quick Net Connect(QNC), as further described herein.

[0080] Upon delivery to a service provider, the CM manager 240 goesthrough basic administrative configuration before supporting NBSactivities. Initial configuration involves basic system configurationsuch as assigning passwords to operating system level accounts forroot-level system administration and configuring CM manager 240 networkinterfaces for proper operation on the local wireless infrastructurenetwork.

[0081] Once the CM 104 is configured, general net administration cantake place. Net administration functions take place through an HTML orother network interface built over TCP/IP. The administrationworkstation 224 interacts with the CM core complex 204 using aconventional World Wide Web (WWW) browser. Administration can take placelocally or remotely (anywhere on the Internet, or via dial-up). However,the underlying transport path for administrative access is typicallyTCP/IP. Also, multiple (at least three) simultaneous administrationconnections are allowed.

[0082] Upon connecting to the CM core complex 204 for the purpose of netadministration, the administrator workstation 224 successfullyauthenticates itself to insure that only authorized administrativeactions are accepted. Different levels of access are accommodated; forexample, authorized net members may connect directly to the CM'sadministrative interface 248 to modify specific net membership lists.More generic administrative privileges are generally reserved forspecific administrative accounts. For clarity, administrative actionsare generally separated into those that deal specifically with userdefinitions and those that define nets. A user definition comprisesinformation such as the username, unique CD cellular system identifier,CD phone number, and user e-mail address. A unique user identifier isdefined that may be passed to the CD and used to uniquely identify theuser in signaling messages. A net definition comprises information suchas the net-address, net hang-time, private dispatch timeout, and memberlist. A net's member list comprises of information such as of a list ofmember records, which individually contain a user identifier andpriority level. A member with the minimal level of priority typicallyhas listen-only privileges.

[0083] The CM administrator 248 may monitor the current status of netsfor which they have administrative privileges. In particular, the CMadministrator 248 may determine the current list of net participants, aswell as monitor the net's state (active, inactive, dormant, in wake-up,etc.). Whenever the net is active, the CM administrator 248 may alsomonitor the identity of the current talker. Additional statistics andstatus, such as the length of current session, total talk time, meannumber of registrants, etc., may also be available to administratorsthrough the administrative interface.

[0084] The administration server 248 interface comprises of at least twonetwork nodes, or ports. One is a TCP/IP based Hyper Text TransferProtocol (HTTP) interface supporting administrative access through aconventional Java™-capable web browser. The second is a TCP/IP based NBSspecific Command Lime Interface (CLI).

[0085] The administration server 248 makes all administrative functionsavailable to a generic web browser via a HTTP web server interface withone or more pages formatted using an Internet readable medium, such asHyper Text Markup Language (HTML) syntax. At least one of theadministrative pages may include a reference to an embedded Java™applet. Some administrative functions may optionally be performedthrough HTTP GET and POST commands issued by the web browser usingconventional HTACCESS authorization mechanisms. The administrativefunctions supported are generally a subset of those supported by the CLIinterface.

[0086] The HTTP interface may be used to deliver a Java™ applet to theweb browser. The applet may then rely on the administrative server 248CLI interface to provide additional administrative functionality to theuser through a web browser interface. Prior to being granted access tothe CLI interface, a potential administration workstation 224 connectingto the administrative server 248 CLI interface is authenticated. In apreferred embodiment, the CLI interface is reachable on a well-known,fixed, TCP port address and is able to simultaneously manage multipleCLI sessions.

[0087] The data base server 232 is responsible for storage of netinformation and parameters, net user information, status informationassociated with the MCUs 208 and 212, and the CM node 228. The databaseserver 232 also serves this information to the remainder of the CM 104,such as the SIP server 236 and other modules that need such information.The database server 232 maintains databases that capture informationthat support NBS net activities, including an NBS net database portionand an NBS user database portion. Information supporting administrationactivities and privileges may be stored in either database, or a thirdfunctionally distinct database. The database server may be furthersubdivided into a user portion and a net portion.

[0088] The CLI interface supports administrative functions such as CLIcreate user/net, delete user/net, modify user/net, list/show user,list/show net, status and help. The Create User function allows theadministration server 248 to create new users in the user portion of thedatabase, including specifying all user record fields. The Delete Userfunction allows the administration server 248 to delete existing userrecords in the user portion of the database 232. The Modify Userfunction allows the administration server 248 to modify existing userrecords in the user portion of the database 232, including modifying allrecord fields for a specific user.

[0089] The Create Net function allows the administration server 248 tocreate new nets in the user portion of the database 232, includingspecifying all net definition parameters. The Delete Net function allowsthe administration server 248 to delete existing nets in the userportion of the database 232. The Modify Net function allows theadministration server 248 to modify existing nets in the user portion ofthe database 232, including modifying all net definition parameters fora specific net. The List User function allows the administration server248 to list all users, by user name, dial number, and user identifier,in the user portion of the database 232.

[0090] The List Net function allows the administration server 248 tolist all nets, by net-address and net identifier, in the net portion ofthe database 232. The Show User function allows the administrationserver 248 to show all fields for a specific user identified by theuser's user identifier. The Show Net function allows the administrationserver 248 to show all fields for a specific net identified by the net'snet identifier or net address. The Status function allows theadministration server 248 to query for a static status report for aspecific net. The Status function may also allow the administrationserver 248 to query for real-time (updated) reports. In particular, thestatus function identifies the current list of net participants, thecurrent talker, the presence or absence of media traffic, and identifiesany and all media signaling messages sent or received by the CM. TheHelp function allows the administration server 248 to query for a briefhuman-readable summary of each supported CLI command, including usageand syntax description.

[0091] The NBS user portion of the database 232 tracks individual usersof NBS. The user records contained within the database 232 may or maynot necessarily be members of net's defined in the CM's net portion ofthe database 232.

[0092] Each record in the user portion of the database 232 is comprisedof fields such as user name, user identification, vocoder list, dialnumber, user type, CRTP support, CD user address, and CD pretty goodprivacy (PGP) public key. The vocoder list is a list of vocoderssupported by the subscriber's CD. The list may include vocoders notsupported by NBS. The dial number is the dial number of the subscriber'sCD. This field is empty, or null, for generic Internet users. The usertype is a type field describing whether the user is a CDMA cellular orgeneric Internet user. Users who connect via PSTN dial-up are consideredgeneric Internet users. The CRTP support is a flag indicating whetherthe CD supports and attempts to negotiate CRTP Header Compression overPPP when connecting. This flag is valid for cellular as well as PSTNbased users. The CD user address is the globally unique user address forthe CD. A CD known by multiple user addresses will have multiplecorresponding entries in the user portion of the database 232. The PGPpublic key is the key associated with the CD user address.

[0093] The NBS net database defines the set of nets known to the CM. Thenet portion of the database 232 also lists the defined members of eachnet; that is, those users who may request to join and becomeparticipants in a net. Each record in the net portion of the database232 is comprised of a variety of fields. Fields include a netidentifier, which is a unique integer identifying the net within thecontext of the CM. Fields also include a net-address, which is the SIPcompatible net-address of the net. Net owner(s), a non-empty list ofusers, is identified by user identifiers who have administrativeprivileges (defined separately) for the net. Also, net security statusis a field for a flag indicating whether the net is clear or secure.

[0094] Fields also include arbitration scheme, which is a unique valueidentifying the arbitration scheme used to resolve PTT arbitrationconflicts between net participants. Net vocoder describes a field havinga unique value identifying the standard vocoder shown in the net'sadvertised session description. Defined members of the net have thisvocoder listed in their list of supported vocoders. PTT fail-safetimeout is the maximum number of seconds a net participant may transmitmedia to the net before the CM revokes control of the floor with a PTXdenial message. Hang-time timeout value is the maximum number of secondsthe net may remain idle before the CM will place it in the dormantstate. PTX Dormancy Response timeout value is the maximum number ofseconds the CM waits after determining that a dormant net's floor can begranted before transmitting the PTX grant response to the requesting CD.Wake-up timeout value is the maximum number of seconds the CM waits fornet participants to respond to the AYT “wakeup” message before grantingan outstanding PTT request. Late-riser timeout value is the maximumnumber of seconds the CM waits for a CD to respond to the CM's AYT“wake-up” message before the CM will remove the non-responding CD fromthe net's list of active participants. AYT timeout value is the maximumnumber of seconds the CM waits for a CD to respond to a CM's AYT messagebefore the CM removes the CD from the net's list of active participants.Media channels list is a list of media channels, including payloadspecifications, for the net (nets list at least one media channel, whichtransports voice).

[0095] The net membership list defines the set of users who may requestto join the net as participants and associated net specific privileges.Each entry in the list contains fields such as the user identifier,which is a unique identifier of a user listed in the CM's user database232. Fields also include the user net priority level, which is theuser's priority level to be used by the net's PTT arbitration algorithmin resolving PTT conflicts. A priority level of zero indicates that theuser has listen-only privileges and may never be granted control of thenet. Fields may also include a user authorization list, which detailsthe authorization privileges, if any, the user has for the net.Privileges may include the ability to add, edit, or modify entries inthe net's membership list and the ability to modify other netparameters.

[0096] Each CD maintains a database, also known as the group-list,identifying known nets that the CD may request to join. Each entry inthe CD database includes fields such as net address, net securityadvisory flag, net traffic encryption key, and dormancy babysit timer.The net address is the net's formal SIP net-address that the CD uses torequest to join the net as an active participant. The Net securityadvisory flag is the clear/secure advisory flag distributed by the CM'sSIP server 236 in its list of available nets or set by the user toindicate that a net defined to carry Type IV secure media traffic. Thenet traffic encryption key is the traffic encryption key used to encryptand decrypt all media traffic for Type IV secure nets. The dormancybaby-sit timer is the length of the interval, in seconds, the CD willwait when in the Dormant/Idle state between transitioning to theConnected state, confirming that the packet data call remains valid andthe base station has not unilaterally dropped the connection.

[0097] The MCU node 208 comprises of an MCU 252, a MCU node manager 256and the local log server 260. The MCU node 208 and 212 may alsooptionally comprise of an additional MCU 264. The MCU node 212 issubstantially the same as the MCU node 208. For description purposes,only the MCU node 208 is discussed herein. The MCU 252 is responsiblefor control of a single active net. The MCU supports SIP, mediasignaling, and media interfaces for the net, and provides thefunctionality associated with the normal operation of the net. Each MCUnode 208 may have a pool of MCUs 252 that may be directed to manage netsas appropriate. Each MCU 252 provides a MCU management interface tosupport functions such as starting, stopping, and status reporting.

[0098] The MCU node manager 256 monitors the operation of the MCU node208 and manages the operation of each MCU 252 on its MCU node 256. TheMCU node manager 256 also provides an external interface to the CM corecomplex 204 to allow for startup and/or shutdown, assigning a net to thenode, and sharing of status information. The local log server 260locally records all log events for the MCU node 208. The local logserver 260 also responds to requests from the central log server 244 viaits log events interface. Requests include uploading certain eventclasses or priorities. In order to prevent loss of events, the messagesare stored in the local log server 260 until an acknowledgement isreceived by the central billing log server 244.

[0099] The DNS server 216 provides name services to the NBScommunication devices. The DNS server 216 may service SRV recordrequests. The DNS server 216 may be located anywhere on the network. Inan embodiment, the DNS server 216 is a part of the CM core complex 204.

[0100] Each CD maintains a list of nets, or a group-list, internallyrepresenting the set of known nets in which the CD can participate. Thelist is non-volatile, but may be updated as needed either throughinteractions with a CM 104 or interactively by the user. The user isalso able to determine who and how many users are either active orinactive in the net. The NBS group-list maintained internally by a CD isanalogous in function to the list of names and dial-numbers maintainedin the phonebook and used to facilitate voice-services. The NBS grouplist may be integrated with the phone's conventional phone book. Ineither case, the act of selecting a net from the group list instructsthe phone to attempt to join the selected net.

[0101] In order to participate in a specific NBS net, each CD initiallyrequests that the CM add itself to the list of active net participantsfor a specific net. Thus, each CD initially is aware or is able to learnthe net-address of any nets in which it wishes to participate. Further,each CD initially knows or is able to be configured with the address ofa top-level SIP server 236 to which SIP requests may be sent.

[0102] Net addresses may be provisioned or learned by a CD in severaldifferent ways. For example, in an embodiment the CD may be initiallyprovisioned with the address of a known or default top-level SIP server236 that provides a current list of nets in which the CD canparticipate. The CD may also be provisioned with a group-list, whichdefines at least one netaddress in which the CD is a member. The CD maylater send a request to the top-level SIP server 236 to update itsgroup-list. In the event that no explicit NBS provisioning has takenplace for the CD, the user may be provided with a top-level SIP server236 and net address to interactively enter into the CD before using NBS.The user may also interactively enter additional net-addresses to agroup-list that has already been provisioned with entries. Such aconfiguration step is analogous to entering personal names anddial-numbers into the conventional phone-book.

[0103] Note that although users may interactively enter a net-addressinto the CD group-list, the corresponding net and top-level SIP server236 are preferably in existence and the user is needed to be listed as amember of the net in order for the CD to be able to successfullyparticipate in the net.

[0104] The CD may also be provisioned with the IP network address of theprimary Domain Name Service (DNS) server 216, to which the CD can sendDNS queries. Typically, the address of the DNS server 216 operated by aCDMA cellular carrier is provisioned. The CD may also be provisionedwith the IP network address of an alternate DNS server.

[0105] In order to support SIP authentication, the CD may be provisionedwith a unique PGP user-id and secret key that it can use to sign SIPtransactions when requested by the CM 104. The PGP user-id may also beused as the CD user address for generic SIP transactions.

[0106]FIG. 10 illustrates the high level functionality of the groupservices module 500 of the CD. Normally, the group services module isinitialized to a default idle state 504 when the CD is powered on. Fromthe idle state 504, the CD may transition to other states that allow itto actively participate in NBS nets.

[0107] The user may wish to temporarily disable NBS services through amenu option within the CD user-interface. If the user has disabled NBSservices, the group services module defaults to a disabled state 508when the CD is powered on. When disabled, the CD does not attempt toautomatically join in any NBS nets. Further, the CD does not perform anyNBS specific SIP transactions (the CD may maintain registrations orperform other SIP transactions for other IP based telephony applicationsresiding within the CD).

[0108] Optionally, group services may be hidden entirely from the userby provisioning group services within the CD to an unequipped state 512.The unequipped state disables group services, where an equipped stateenables group services. Once unequipped, the CD requires administrativeprovisioning to equip group services. When group services areunequipped, the NBS group services functionality and related userinterface features are not available to the user.

[0109] The CD may support over-the-air provisioning to equip NBS groupservices. In the event that the group-list of the CD contains more thanone net-address, no more than one net-address may be identified as adefault net 514. If a net-address is selected, the CD attempts toautomatically transition from the idle state 504 by attempting to jointhis selected net shortly after the CD is powered on.

[0110] When the CD is connected, the CD cycles from a quiet state 516, alisten state 520, a talk state 524 and a dormant state 528 based onwhere the user is in the push-to-talk system as described with respectto FIG. 16.

[0111] The NBS relies on call signaling syntax and semantics as definedby the SIP to advertise available net-addresses and provide mechanismsby which an individual CD can formally join or leave nets. The CM 104,along with other functional entities, includes the a top-level SIPserver 236, one or more multipoint control units (MCUs) 252 andassociated SIP user-agent servers, and user and net portions of theadministration database 232. The top-level SIP server 236 acts as aknown rendezvous point to participate in the system. Each MCU 252performs media signaling and media traffic switching for one or morenets. The database 232 stores and provides known user, administration,and net-address definitions and may serve multiple CM installations orbe accessed remotely.

[0112] Each CD is provisioned with a list of net-addresses, and one ormore top-level SIP server 236 addresses. If the group-list is empty, theuser may interactively specify the address of an existing net. If notop-level SIP server 236 is defined, the user may interactively specifythe address of a top-level SIP server 236. Once the top-level SIP server236 address is known, the CD may request an updated list of netsavailable to it by placing a call using the SIP INVITE method to apre-defined SIP destination.

[0113] The top-level SIP server 236 may redirect the request to aninternal destination or respond to it directly. The INVITE response tothis call includes the current list of nets available to the CD. The CDuses this list to update its internal group-list.

[0114] After a net has been selected, the CD attempts to join the netusing the SIP INVITE method by specifying the net-address as theinvitation destination and sending the request to the top-level SIPserver 236. The top-level server 236 attempts to map the net-address toa known destination and, if successful, redirects the CD to thecorresponding SIP user-agent server of the MCU 252. If no mapping isavailable, the invitation generally fails.

[0115] Normally, the destination SIP user-agent server of the MCU 252confirms that the CD is a member of the selected net and responds to theinvitation, embedding a description of the media traffic and signalingparameters to use to participate in the net in the content of itsresponse. The SIP user-agent server of the MCU 252 may also reply withan error if it is unable to confirm the CD as a legitimate member of thenet or if some other error condition arises, such as a failure thatprecludes normal net operation. If the invitation is accepted, the CDacknowledges the response through a message, such as the SIP ACK method.Note that other transient response codes that indicate call progress mayalso be received by the CD while the invitation is being processed.

[0116] The CD is responsible for updating its group-list to the set ofthe nets in which it may participate. The user may command the CD toquery the database 232 of the CM 104, even when no net-address isselected, for the purpose of receiving updates to its group-list. If theCD determines that it has been added or removed from a net, it brieflydisplays an appropriate message to the user (for example: “Added togroup X”) and/or possibly prompt for user interaction. If the CDdetermines that is not a member of any net, it will similarly inform theuser. The CD may automatically incorporate new net addresses into itsgroup-list but may prompt the user before deleting addresses of nets inwhich it has lost membership from the group-list.

[0117] Generally, no more than one net in a CD's group-list may beidentified as selected at one time. A default net may be initiallyselected or the user may select a net from the group-list.

[0118] The CM's SIP user-agent server of the MCU 252 response to anINVITE request to join a net includes, as embedded content, the net'smedia and real-time media signaling destination addresses, as well asother net parameters (such as media payload format descriptors). Onceconfirmed, the CD briefly displays feedback to the user, indicateswhether the user has listen-only privileges, and enables group servicefunctions. If the CM 104 determines that the CD is not a member of theselected net, or an error or other exceptional condition occur, the SIPserver 252 responds with a corresponding error response. When such aregistration is rejected, the CD briefly displays a corresponding errormessage and group service functions remain idle. If no net is selected,group services within the CD remain idle.

[0119] As part of activating group services, the CD initializes andopens its RTP media traffic channel 128 and the separate NBS mediasignaling channel 124 to the CM destination addresses provided in asuccessful invitation response. Once these channels have beeninitialized, groupservices are activated on the CD 108 and it enters thegroup-service quiet state 516 with the ability to receive voice trafficfrom the net and request permission to send voice traffic to the net.

[0120] With group services active, the CD 108 monitors its media traffic128 and signaling channels 124 to the CM. Voice data received on themedia traffic channel 128 is decoded and presented using a CD 108far-field speaker or an ear-piece accessory, according to the currentuser configuration. The CD 108 displays the identity of the currentspeaker, as identified through real-time media signaling 124. If theidentity of the current speaker is unavailable, the CD 108 displays thecurrent selected net name as listed in the group-list. The CD 108 mayalso tabulate media traffic statistics (for example, total time spenttalking, listening, and monitoring, estimated media traffic receiptpacket loss) and make these available to the user as a diagnostic usinga menu option. While receiving traffic from the net, the CD 108transitions to the group-services listen state 520, returning to thequiet state 516 when voice traffic stops.

[0121] At any time, the user may request permission to speak to the netby depressing the PTT button and causing the CD 108 to signal the CM 104(specifically, the MCU 252) with a floor-control request. The PTT buttonmay be any type of activation command, including, but not limited to,depressing a key or sequence of keys, voice activation, a switch, atoggling device, or dials. The MCU 252 responds by either granting ordenying the request. If the CD has listenonly privileges, such as CD112, (that is, the CD has a priority-level of zero within the selectednet), the request is denied. If denied, the CD 112 alerts the user withan error tone, displays a suitable error or explanatory message, andreturns to the quiet state 516. The CD insists that PTT be released anddepressed again before attempting another floor-control request. Ifgranted, the CD 112 enters the group-services talk state 524, signalsthe user with, for example, a brief audible chirp, and beginstransmitting voice traffic to the CM 104 for as long as PTT is keyed.The CM 104 may asynchronously signal the CD 112 (while PTT is keyed)that it has lost control of the floor. Upon receipt of such a signal,the CD 112 aborts transmitting voice traffic and alert the user with anerror tone until PTT is released, at which point it returns to the quietstate 516. Otherwise, once PTT is released, the CD 112 signals the CM104 that it has released the floor and returns to the quiet state 516.

[0122] A user may switch to a different net by selecting another netfrom the group-list whenever group-services within the CD 108 is in thequiet state 516, the listen state 520, or the dormant state 528. When anew net is selected, the CD 108 signals the CM 104 to remove it from thecurrent net through SIP call-setup mechanisms and then follows similarprocedures to join the new net. If the process of joining the new netfails, the CD 108 is no longer a member of any nets and group serviceswithin the CD 108 returns to the idle state 504.

[0123] If the CM 104 determines that the CD 108 requesting the floor ofa particular net is the only registered member of the net in question,the CM 104 denies the floor-control request and signal an error message,such as a lonely-user error, which the CD 108 displays to the user.Although a net may exist with only one registered member, a net cannotrelay voice traffic unless there are least two registered members.

[0124] The NBS application is based on two distinct application-levelprotocols: the Session Initiation Protocol (SIP) call signaling asdescribed with respect to FIG. 11 and NBS Media Signaling as describedwith respect to FIGS. 12-14. SIP is used exclusively for call signalingand call setup. Media signaling carries PTT requests (FIG. 12) managesnet dormancy (FIG. 13), and resolves PTT arbitration conflicts (FIG.14).

[0125] SIP call signaling 350 is illustrated in FIG. 11. The SessionInitiation Protocol provides NBS application-layer control (signaling)for discovering, joining and leaving NBS nets using the SIP serverinterface 236 of the CM 104. To join a net, a CD 352 invites the net100, by name, to participate in a call, through the top-level SIP server236. To leave the net 100, the CD 352 sends a corresponding “good-bye”to the net.

[0126] The CD 352 determines the IP address of the top-level SIP server236 by using the DNS 216 to resolve the provisioned primary or secondarySIP server addresses into Internet network addresses, if necessary. Asan optional alternate approach, SIP conventions allow the CD 352 toquery the DNS 216 for service records associated with the NBS hostsystem domain portion of the net address and contact the SIP server 236at the returned address(es).

[0127] By default, the CD 352 attempts to contact the SIP server 236using a default SIP port, unless alternate port information isdetermined through DNS 216. Prior to attempting to join a net, the CD352 may place a call using the SIP INVITE method to request an updatedlist of available nets.

[0128] For example, the CD 352 that has brought up an over-the-airconnection is assigned an IP address and wishes to determine its currentlist of available nets. This opens a UDP/IP connection to the SIP serverport and issues a request. The request to obtain an updated list of netsis addressed to a special destination. When appropriate, the CD 352 alsoincludes additional application-specific headers identifying the CDMAnetwork and system from which a CDMA cellular based CD 352 is obtainingservice.

[0129] The CD 352 may also include a header to indicate that the CD 352expects that the SIP server 236 understands and supports NBS services.The option value distributed with the header can also be used by the CD352 to inform the server 236 of a specific version or type of NBSservices that the CD 352 expects the server 236 to support.

[0130] The CM's top-level SIP server 236 may redirect an invite request356, using SIP redirection mechanisms, to a destination specificallydefined to receive and respond to requests for net information. Uponreceiving such a redirection, the CD 352 acknowledges (ACK) the response357 and re-sends the request to the redirected destination.

[0131] The CD 352 may need to determine the appropriate SIP contactpoint for the redirected address, through DNS mechanisms. To simplifythis process for the CD 352, the server 236 may specify the redirectdestination explicitly using its Internet network address. Once anINVITE message 354 requesting a list of nets is successfully receivedand accepted by the server 236, the server 236 delivers an INVITErequest response 356.

[0132] The INVITE request response 356 includes in its content a list ofrecords defining the set of nets that the CD 352 may subsequently join.The server 236 queries its net database 232 for nets that list therequesting CD 352 as a defined member to form the response 356 to theINVITE request 354. Nets are identified within the content using anapplication defined record format that includes the formal net-addressof the net. Nets may be listed in any order.

[0133] The server 236 may be unable to successfully respond to the CD352 for a variety of reasons. In such circumstances, the server 236delivers an appropriate SIP status code in place of the INVITE response356. The CD 352 should be prepared to accept and interpret such statuscodes, taking appropriate action (such as displaying an error message onthe CD 352 user interface display) in the case of any fatal errors. Theserver 236 may also preface a successful INVITE response 356 withinformational status responses indicating the progress of theregistrations. The CD 352 may accept and interpret informational statuscodes that preface successful registrations.

[0134] The CD 352 requests to join a net by issuing a SIP INVITE request358 to the CM manager 240 through the server 252. If the CD 352 does nothave an open UDP/IP connection to the SIP server 252, it will open a newUDP/IP connection to the SIP server port.

[0135] The CD 352 is prepared to be redirected by the top-level SIPserver 236 and re-issue the request to the redirected destination ifnecessary. The CM's top-level SIP server 236 redirects any incomingINVITE request as appropriate to the MCU's SIP server 252 currentlyassociated with the net in question. The CD 352 may be redirected morethan once.

[0136] The INVITE request 358 may include a description (as messagecontent) of the media sources that originates with the CD 352, assumingthe invitation succeeds. If included, the description is included asmessage content and described using field constructions.

[0137] The session description is delivered in a format compatible withthe Session Description Protocol (SDP). After defining the SDP version(v), the session description includes a mandatory origin (o)description. The CD 352 may use any convenient mechanism for choosingthe values for the session identifier and session version. Providing anestimate of the current time is one possible way of defining the sessionidentifier. Connection data (c) is specified by defining the networktype, address type, and connection address. The CD 352 uses the IPaddress with which it labels (or source) media traffic as the connectionaddress. The CD 352 uses the name portion of the net's net-address asthe session name (s). The CD 352 specifies the lifetime (t) of thesession by providing its best estimate of the start or current time,preferable in Network Time Protocol (NTP) format, and indicates that thesession is unbounded (0). The media format (m) description defines themedia type, source port, transport protocol, and payload format that theCD 352 intends to use to transmit to the net. Finally, the sessiondescription uses an attribute (a) type definition to indicate that theCD 352 expects the session to be operated as a NBS conference. Theserver 236 should confirm that the invited to address is indeed a validNBS net address before granting the invitation.

[0138] To indicate a successful invitation, and specifically inform theCD 352 that it has been added to the list of participants for theinvited net, the server 236 delivers an INVITE response 360.

[0139] A successful INVITE response 360 includes the primary sessiondescription for the invited net, which describes supported media trafficports and formats using SDP syntax. The session description includes aconnection (o) description that defines the network address to which allmedia signaling and traffic should be sent. The net's media destinationnetwork address is not necessarily the same as the SIP user-agentserver's network address resolved using DNS from the net's net-address.

[0140] The session description describes all media and destination mediaports. The session description should also include an identifierassigned to the CD 352 by the MCU 252 for the purpose of identifyingmedia signaling messages transmitted by the CD 352 as part of itssubsequent participation in the net. The value of this identifier isunique among all active participants on a given net and should thus begenerated dynamically. The CD 352 does not necessarily cache thisidentifier between successful SIP invitations.

[0141] The session description may also include an NBS protocol versionannouncement indicating the revision level to which the net's mediasignaling adheres. Such an announcement may be implemented by extendingthe value of the type attribute field or defining a new attribute, whosevalue is the protocol version number.

[0142] After receiving a successful INVITE response, the CD 352 confirmsthe invitation by sending a SIP acknowledge (ACK) request 362 back tothe net's MCU's SIP user-agent server 252. After transmitting the ACKrequest 362, the CD 352 may close its TCP connection with the SIPserver. Prior to the ACK request 362 being transmitted, the CD 352initializes its media signaling and traffic ports according to thesession description delivered in the INVITE response 360.

[0143] At any time after the CD 352 has transmitted the SIP ACK message362 in response to a successful INVITE response 360, the CD 352 mayformally terminate its participation in the net by sending a SIP BYEmessage 364 to the net's user-agent server 252. Prior to sending the BYEmessage 364, the CD 352 may need to open a TCP connection to theuser-agent server 252. The BYE message 364 is acknowledged by the CMwith a BYE response message 366. Once the BYE response message 366 isacknowledged, the CD 352 may close its UDP connection with theuser-agent server 252. Prior to acknowledging the BYE response message366, the user-agent server 252 removes the CD 352 from the indicatednet's list of active participants.

[0144] In general, a SIP user-agent client of the CD 352 may use theOPTIONS method to query a SIP server's capabilities. In particular, theCD 352 might wish to query an arbitrary SIP destination to determinewhether the destination provides NBS call-signaling support.

[0145] The CD 352 may wish to abort a pending INVITE request 358 priorto receiving the INVITE response 360 and sending the acknowledgement362. In such circumstances, the CD 352 may use a SIP CANCEL (not shown)method to gracefully abort the call. Both the top-level SIP redirectserver 236 and the CM's SIP user-agent server 252 support the CANCELmethod.

[0146] For example, the CD 352 may use the CANCEL method to abort anINVITE message 358 in progress if the user decides to place avoice-services call and presses send before the INVITE message 358completes. In such a circumstance, rather than wait for the INVITEresponse 360 to complete and immediately send the BYE message 364, theCD 352 may simply immediately CANCEL the INVITE message 358 and proceedto place the requested voice-services call.

[0147] After the CD 108 has successfully negotiated entry into thecurrent membership of a NBS net using SIP, all real-time call controltakes place through point-to-point application level media signalingmessages exchanged between each CD 352 and the net's MCU SIP server 252.

[0148] Media signaling messages are transported using the protocol stackdepicted in FIG. 4, and in accordance to the sequence depicted in FIG.12. FIG. 12 illustrates a media signaling message sequence 368. A PTTrequest message 370 is sent by the CD 352 to the SIP user agent server252 of the MCU node 208 and signals a user's desire to broadcast media,usually voice, to the net. Normally, the PTT request message 370 is sentfor each press of the CD 352 push-to-talk button to denote afloor-control request. In addition, a PTT release message is sent by theCD 352 to the SIP user agent server 252 to denote the normal release ofthe “floor” when the user releases the CD 352 push-to-talk button.

[0149] The PTT message comprises of fields such as the opcode, id, src,and reserved. The opcode field defines whether the PTT message is afloor-control request or release message. The id field provides a uniquemessage identifier to allow subsequent PTT release and PTX messages toreference a specific PTT request. The id should be unique within theregistration session of a particular CD 352. The src field uniquelyidentifies the CD 352 that sends the PTT request 370 to the SIP useragent server 252. The reserved field reserves space in the PTT message370 for future capabilities.

[0150] The CD 352 expects to receive at least one PTX response message372 for every transmitted PTT request 370. If a PTX response 372 is notreceived within a predetermined timeout period, the CD 352 assumes thePTT request 370 was lost in transit and retransmits the PTT message 370using the same PTT id.

[0151] If a PTX response message 372 is never received from the SIP useragent server 252 within a predetermined number of retransmits, the CD352 assumes that SIP user agent server 252 is no longer reachable,transitions to NBS idle mode, and indicates an error condition to theuser. In a preferred embodiment, the CD 352 uses a different PTT id forthe request and release messages.

[0152] The PTX message 372 is sent by the SIP user agent server 252 to aCD 352 to acknowledge and respond to a previous PTT request 370, as wellas to signal asynchronous floor-control events. The SIP user agentserver 252 uses the PTX message 372 to respond to a PTT floor-controlrequest or release. The PTX message 372 includes information such as towhether the referenced floor-control request was granted or denied. Whenresponding to a PTT floor-control release 370, the PTX message 372 isused to indicate confirmation of receipt only. The SIP user agent server252 may also use the PTX message 372 to asynchronously deny a previouslygranted floor-control request (when a higher priority CD 352 issues afloor-control request, the PTX grant expires (i.e., times out), or someother event occurs requiring that control of the net's floor berevoked).

[0153] The PTX message 372 comprises fields such as opcode, id, action,status, and expires. The opcode field defines whether the PTX message372 is a synchronous response to an outstanding PTT request, or if it isan asynchronous message indicating an error or priority arbitrationconflict. The id field references a previously received PTT request. Theaction field indicates whether the PTX message 372 is granting, denying,revoking, or confirming control of the net's floor. The status fieldprovides additional information explaining the PTX action, particular incases when the PTX message 372 denies, revokes, or cannot act upon theprior PTT request. The status field may indicate that a higher prioritytalker has been granted control of the net, or that the CD 352 is notlisted as a net participant and hence is not allowed to submit mediasignaling requests for the net. The expires field represents the maximumduration, in whole seconds, for which the control of the net's floor isgranted to the receiving CD 352. The SIP user agent server 252 startsits timer from the instant it sends the PTX message 372 response, notwhen the CD 352 begins sending media traffic. The value of the expiresfield is a configurable net parameter.

[0154] The CD 352 does not explicitly acknowledge receipt of the PTXmessage response 372. Instead, if the transmitted PTX message response372 is lost, the CD 352 PTT retransmit timer expires and the CD 352retransmit its PTT request 370. Since the retransmitted PTT 370 has thesame id as the lost PTX response 372, the SIP user agent server 252responds by re-sending the lost PTX message response 370, rather thantreating the retransmitted PTT message request 372 as a separatepush-to-talk request event.

[0155] A PTA message 374 is sent by the SIP user agent server 252 toeach CD 352 currently participating in a net to announce the identity ofthe source of pending media traffic. A PTA message 374 is also used toformally announce the end of a talk-spurt.

[0156] The PTA message 374 comprises fields such as opcode, talker, andreserved. The opcode field indicates whether the PTA message 374 isannouncing the granting (or release) of the floor to (or by) the CD 352identified by talker. The talker field identifies the CD 352, whichsources media traffic to the net until the next PTA message 374 is sent.The reserved field reserves space in the PTA message 374 for futurecapabilities.

[0157] The CD 352 whose PTT floor-control request 370 was successful mayor may not receive a PTA message 374 announcing it has control of thefloor. The message may arrive before or after it receives thecorresponding PTX response 372, since UDP does not necessarily preservedatagram ordering. However, the SIP user agent server 252 sends the PTAannouncement 374 before it expects to begin forwarding media (in thecase of a PTA grant announcement). It is recommended that the requestingCD 352 ignore received PTA messages 374 that announce it has won controlof the floor and rely only on the receipt of a PTX grant messageresponse 374 to determine whether it can begin transmitting media to thenet.

[0158] An “are you there” AYT message 404 (FIG. 13) is sent by the SIPuser agent server 252 to an individual CD 352 in order to confirm thatthe CD 352 in question is reachable using IP. A collection of AYTmessages 404 may also be sent to a group of net participants in order tosignal that a net is no longer in dormant mode.

[0159] The AYT message 404 comprises fields such as opcode, id, andreserved. The opcode field indicates whether the MCU node 208 is sendingthe AYT message 404 to determine whether the CD 352 is still reachableor if the SIP user agent server 252 is using the AYT message 404 trafficto bring the net's associated CDMA cellular traffic channels out ofdormant mode. The id field provides a unique message identifier to allowa subsequent “I am here” IAH response message 408 to reference aspecific AYT request message 404. The id may include a timestampreference for generating latency estimates. The reserved field reservesspace in the AYT message 404 for future capabilities.

[0160] The CD 352 may or may not be in dormant mode when an AYT message404 is sent. In all cases, the CD 352 responds to a received AYT message404 with an IAH response message 408.

[0161] The SIP user agent server 252 assumes that the CD 352 generallyresponds to an AYT message 404 with an IAH response 408. If an IAHresponse 408 is not received within a reasonable timeout, the SIP useragent server 252 transmits a new AYT message 404 with a new id. If aftera configurable number of retransmits, a response to the AYT message 404is not received from the CD 352, the CD 352 is assumed to be unreachableand the SIP user agent server 252 removes it from the current list ofnet participants. Future media signaling messages from the removed CD352 will be ignored (or will generate an error response) until the CD352 successfully re-joins the net.

[0162] The IAH message 408 is sent by the CD 352 to the SIP user agentserver 252 to acknowledge receipt of a previously sent AYT message 404.The IAH message 408 comprises fields such as id, src, and reserved. Theid field references a previously received AYT message 404 that the CD352 is acknowledging. The src field uniquely identifies the CD 352 thatsends the IAH message 408 response to the SIP user agent server 252. Thereserved field reserves space in the IAH message 408 for optionalcapabilities.

[0163] The SIP user agent server 252 assumes that the CD 352acknowledges all received AYT messages 404 with an IAH response message408. If the referenced AYT message 404 was sent to confirm that a CD 352remains connected in the NBS quiet state, passively monitoring NBS mediatraffic and signaling, the SIP user agent server 252 notes the time ofthe IAH receipt 408 for future reference.

[0164] Since the SIP user agent server 252 is responsible for definingthe value of the id field, the SIP user agent server 252 may use the idto determine and track whether a specific CD 352 remains reachable.

[0165] The ZZZ or sleep message (illustrated in FIG. 13 as referencenumeral 412) is sent by the SIP user agent server 252 to the CD 352 toencourage the CD 352 to release its over-the-air resources and enterdormant mode. The CD 352 may choose to ignore this message (especiallyif it is concurrently supporting other packet applications).

[0166] The ZZZ message comprises fields such as id and reserved. The idfield provides a unique message identifier to allow the CD 352 todifferentiate between multiple receipts of the ZZZ message. The reservedfield reserves space in the ZZZ message for optional or futurecapabilities.

[0167] The CD 352 does not acknowledge receipt of the ZZZ message. Errorrecovery is generally not attempted if the ZZZ message is lost. To guardagainst a ZZZ message being lost, the SIP user agent server 252 may sendmultiple copies of the same ZZZ message to an individual CD 352. The SIPuser agent server 252 insures that copies of the same sleep message aresent within a defined interval, and the CD 352 waits for a period longerthan this interval from the time the first sleep message (with a new id)is received before releasing its over-the-air link and transitioning toa dormant state.

[0168] As illustrated in FIG. 15, an ASK message 382 is sent by the CD352 as a query 384 to the SIP user agent server 252 to confirmconnectivity with the SIP user agent server 252. The ASK message 382also allows the CD 352 to determine whether the CD 352 remains listed asa net participant. The CD 352 may confirm its participation after aservice-disruption or other period where it may have temporarily lostconnectivity with the SIP user agent server 252.

[0169] The ASK message 382 comprises fields such as id, src andreserved. The id field provides a unique non-zero message identifier toallow a subsequent FYI response message to reference a specific ASKrequest message. The src field uniquely identifies the CD 352 that sendsthe ASK message 382 request to the SIP user agent server 252. Thereserved field reserves space in the ASK message 382 for optional orfuture capabilities.

[0170] The CD 352 assumes that the SIP user agent server 252 responds toa received ASK message 382 with an FYI response message 386. If an FYIresponse 386 is not received within a predetermined timeout period, theCD 352 transmits a new ASK message 382 with a new id. If after aconfigurable number of retransmits, a response to the ASK message 382 isnot received from the SIP user agent server 252, the SIP user agentserver 252 is assumed to be unreachable and the CD 352 transitions tothe group-service idle state.

[0171] The FYI message 386 is sent by the SIP user agent server 252 tothe CD 352 to acknowledge receipt of a previously sent ASK message 382or is sent asynchronously by the SIP user agent server 252 to inform theCD 352 of an exceptional condition.

[0172] The FYI message 386 comprises fields such as opcode, action,status, id, and reserved. The opcode field defines whether the FYImessage 386 is a synchronous response to an outstanding ASK request 382,or if it is an asynchronous message indicating an exceptional condition.The action field indicates whether the FYI message 386 is confirming netparticipation, informing the CD 352 that it has been administrativelydeleted from the net's member list, or performing some other to bedefined function. The status field provides additional informationexplaining the FYI response 386, particular in cases when the FYImessage 386 indicates that the CD 352 is not a net participant ormember. The id field references a previously received ASK message 382that the CD 352 is acknowledging. In value of the id field is undefinedfor asynchronous FYI responses. The reserved field reserves space in theIAH message 408 for optional or future capabilities.

[0173] The CD 352 generally does not acknowledge receipt of FYI message386 responses. If a synchronous FYI message 386 response is lost, the CD352 sends a new ASK message 382 request. Because the CD 352 does notrequest asynchronous FYI message 386 responses, in a preferredembodiment the SIP user agent server 252 make at least three staggeredtransmissions of any asynchronous FYI message 386 responses.

[0174] A participating CD 352 signals a user's desire to broadcast mediato the net by issuing a PTT message request 376 to the SIP user agentserver 252. The SIP user agent server 252 responds to the PTT request376 with a PTX message response 378 that may either grant or deny therequest. If the request is granted, a PTA announcement message 380 isbroadcast to all net participants. The user-interface of the requestingCD 352 may indicate to the user that permission to talk to the net hasbeen granted as soon as the granting PTX message response 378 isreceived. The CD 352 normally broadcasts media traffic until the userreleases the PTT button at which point it signals the end of thetalk-spurt by issuing a PTT release message 376 to the SIP user agentserver 252. The SIP user agent server 252 responds with a PTXconfirmation message 378 and broadcasts an announcement signifying theend of the talk-spurt to all net participants.

[0175] When any CD 352 has the floor (the right to talk) of a net, thenet is said to be active; otherwise, it is inactive. If a net isinactive for a time exceeding the net's hang-time, the SIP user agentserver 252 may put the net in dormant mode by individually signaling allregistered mobile stations to release their over-the-air trafficchannels. A connection is maintained to allow a floor-control request orother traffic to bring the net out of dormant mode relatively quickly.Net members may ignore “go dormant” messages. The SIP user agent server252 does not explicitly or implicitly track the dormancy status ofindividual net members.

[0176] As illustrated in FIG. 15, the SIP user agent server 252 will“wake-up” a net and bring it out of dormant mode 618 when a successfulfloor-control request 704 is received during dormancy. As soon as thefloor-control request 704 has been granted, the SIP user agent server252 will signal each registered CD 352 by requesting the are-you-there(AYT) message 716 over the media-signaling channel and start an internalwake-up timer 724. Each CD 352 acknowledges receipt of the AYT message716 to the SIP user agent server 252 if it wishes to remain registeredin the net. Optionally, a dormant CD 352 may buffer media traffic 740from the time the user keys PTT until the CD 352 traffic channel is(re)connected. The SIP user agent server 252 may buffer media traffic740 received from the talking CD 352 until the wake-up timer 724 exceedsthe wake-up timeout, at which point, it begins forwarding media trafficto each registered CD 352, including any members that have not yetresponded to the AYT request 716. Thus, both the CD 352 and the MCU node208 have the ability to buffer data until the recipient is ready toreceive the buffered information. In an embodiment, portions of data arestored both in the CD 352 and the MCU node 208.

[0177] The SIP user agent server 252 periodically retransmits AYTrequests 716 to any registered CD 352 that has not acknowledged receiptof the AYT request 716. Once the wake-up timer 724 has exceeded a secondlonger late-riser timeout, the SIP user agent server 252 will unregisterany member CD 352 whose AYT acknowledgement is outstanding and stop thewakeup timer 724. The SIP user agent server 252 ignores duplicate AYTrequests.

[0178] If the CD 352 attempts to join a net that is currently dormant,the SIP user agent server 252 processes the request normally and thensignal the CD 352 to go dormant. The signaled CD 352 may ignore thego-dormant command.

[0179] During periods of extended net inactivity, the NBS allows for apacket data service call to be placed in the dormant/idle state 528 (seeFIG. 10). The SIP user agent server 252 facilitates transitions into andout of the dormant/idle state 528 by independently managing a similardormancy concept for each NBS net 100.

[0180]FIG. 13 illustrates the sequence of media signaling messages withrespect to dormancy 400 between the CD 352 and the SIP user agent server252. In general, a message is sent to all CDs in the net to go dormantbased on a control signal sent from the CM, based on a timer in each CD.As such, resources allocated to the net are released and may be used forother users. On a configurable schedule, the SIP user agent server 252sends a message request (AYT) 404 to each CD 352 for the purpose ofconfirming that the CD 352 in a quiet state remains reachable. Thus, theCM 104 maintains centralized polling of current users of the net andtheir status. This also allows individual CDs to dynamically join orleave the net. The CD 352 responds to the AYT request 404 with a messageresponse (IAH) 408. The AYT messages 404 are not necessarily broadcastto each CD 352 at the same time. The SIP user agent server 252 maystagger sending AYT messages 404 to each net participant to avoidreceiving a flood of simultaneous IAH message responses 408.

[0181] After the net has been idle long enough for the net'sconfigurable hang-time to expire, the SIP user agent server 252broadcasts a ZZZ request message 412 to every net participant. Inresponse, each CD 352 may release its over-the-air resources and enterdormant mode. Net participants need not necessarily respond to the ZZZrequest message 412.

[0182] A successful PTT request 416 by the CD 352 brings the net out ofdormant mode. In an embodiment, a predetermined threshold number ofusers are needed to respond in order to bring the net out of dormancy.Prior to granting the request with a PTX message 420, the SIP user agentserver 252 sends every CD 352 an AYT message request 424 to force eachpreviously participating CD 352 out of dormancy. This is done if the CD352 chose to release its over-the-air resources in response to the ZZZmessage 412, and to confirm that the participating CD 352 still remainsreachable. In another embodiment, After a configurable but fixed delay,defined as the PTX dormancy response timer, the SIP user agent server252 transmits the PTX grant message response 420 to the requesting CD352. Once a second wake-up timer (whose value is generally not less thanthe PTX dormancy response timer) expires, the SIP user agent server 252announces the talker via a PTA message 428 to all net participants andmay begin forwarding media.

[0183] The MCU node 208 is responsible for receiving incoming datapackets from the transmitting CD 352 and for sending duplicate copies ofthe received data packets to other members of the net to which thetransmitting CD 352 belongs. As each data packet is received by MCU node208, it is stored in a memory (not shown). The transmitting CD 352 maybe identified by interrogating the data packet. In one embodiment, an IPaddress representing the transmitting CD is included in each data packetas a way to perform the identification.

[0184] After the transmitting CD 352 is identified, the MCU node manager256 retrieves a list of net members belonging to the net associated withthe particular MCU node 208 from local memory (each MCU is typicallyassigned to one net only). A destination address is associated with eachactive net member, i.e., net members who are presently registered withMCU node 208, in local memory. In one embodiment, the destinationaddress is an IP address. MCU node manager 256 then creates a duplicateof the original data packet, except that the destination addressidentified within the data packet is modified to reflect the destinationaddress of the first net member. Next, MCU 208 creates a secondduplicate data packet, addressed to the second net member. This processcontinues until the original data packet has been duplicated and sent toall of the active net members identified in local memory. During theplay-out of any buffered media, the CM 104 treats the net as active,even if the talking CD 352 has released the floor. Hence, the CM 104does not allow a CD 352 to interrupt the play-out of buffered mediaunless the interrupting CD 352 has higher priority than the source ofthe buffered media.

[0185] Note that the SIP user agent server 252 may receive IAH messageresponses 432 for an extended interval after the net is brought out ofdormant mode and that the SIP user agent server 252 does not wait forall net participants to respond before granting the pending PTT request416. Late responders whose IAH response 432 arrives after the PTX grantmessage response 420 is transmitted remains listed as net participants,but may not receive all initial media traffic and signaling. Any CD 352that does not respond to the AYT request 424 after a third larger (andconfigurable) delay are generally assumed to no longer be reachable andare removed from the net's list of active participants.

[0186]FIG. 14 illustrates a sequence of NBS media signaling messages 440demonstrating a higher priority CD 444 interrupting a lower priority CD442 with control of the net's floor.

[0187] Initially, a lower priority CD 442 submits a PTT message request446 to the SIP user agent server 252 that is granted by the SIP useragent server 252. The SIP user agent server 252 announces that the CD442 has control of the net's floor.

[0188] While the lower priority CD 442 is transmitting media 443, asecond CD 444 attempts to interrupt by sending the SIP user agent server252 a PTT message request 448 for the same net. The SIP user agentserver 252 determines that the second CD 444 has higher priority thanthe talking CD 442 and immediately revokes control of the net's floorfrom the talking CD 442 by sending it an asynchronous PTX denial message454. The SIP user agent server 252 then grants the PTT request 448 tothe higher priority CD 444 with a normal PTX grant message response 452and announces that the higher priority CD 444 has control of the net'sfloor.

[0189] If the SIP user agent server 252 determines that the interruptingCD 444 does not have higher priority, the SIP user agent server 252immediately rejects the PTT request 448 with a PTX message response 452and continues to distribute media 456 from the talking CD to the net'sparticipants without interruption.

[0190] Although the priority assigned to a particular CD is a fixedvalue defined in the database maintained by the SIP user agent server252, the SIP user agent server 252 may use other arbitration algorithmsthat do not necessarily always grant the floor to the highest-priorityrequesting participant, as depicted here. The PTT arbitration algorithmused to arbitrate conflicts can be individually configured on a per netbasis.

[0191] At a minimum, the SIP user agent server 252 supports anarbitration policy that allows a CD to interrupt the current talker onlyif the CD has a priority level that exceeds that of the current talker.An CD with minimal priority can listen to media traffic but never gaincontrol of the net's floor.

[0192]FIGS. 15 and 16 illustrate operation of the CM 104 and CD 352,respectively, during various states. The CM 104 maintains an inactivitytimer for each net, or the hang-time timer 620. When the inactivitytimer 620 reaches a configurable prescribed value, the timer triggersthe CM 104 to place the net in a dormant state 618 by broadcasting amedia signaling message 696 to all net participants. Upon receipt of themessage, a participating CD 352 may release its traffic channel andenter a dormant/idle state 844, or the CD 352 may ignore the message andremain in a connected state 820. In particular, net participants thatare not operating over a channel, such as dial-up PSTN users, shouldignore the media signaling messages.

[0193] The net's hang-time timer 620 does not advance for the durationthat a PTX grant message response 632 is an effect. The timer 620 isreset to zero when the PTX grant message 632 is transmitted and remainat zero until the PTX grant 632 expires or the CD 352 releases the net'sfloor 872. Once the floor is released, the hang-time timer advancesuntil the next PTX grant message response 632 is transmitted.

[0194] If a participating CD 352 enters the dormant/idle state 844, itremains dormant until either packet data addressed to the CD 352 arrivesat the CD 352 MA cellular infrastructure or the CD 352 generates data tosend using the packet data service. The former case may be triggered bytraffic sent to the CD 352 by the CM 104 (908). The latter case may betriggered by the user keying the PTT button to request permission tobroadcast 824 to the net. Other triggers unrelated to NBS are alsopossible.

[0195] The net itself remains dormant until one or more participantstrigger the transmission of a PTT request 704. If the CM 104 determinesit can grant the PTT request message 704 (including performing anynecessary arbitration to deal with multiple requests) it sends a request716 to each listed net participant to trigger a transition out of thedormant/idle state 844. For any specific CD 352, the trigger may or maynot be necessary, but each CD 352 nonetheless responds to the request.In this circumstance, when a net is transitioning out of the dormantstate 618, the CM 104 refrains from sending the initial PTX grantresponse message 756 until a fixed but configurable delay, the PTXdormancy response timer 728, expires. After the timer 728, whose defaultvalue is typically be zero, expires, the CM 104 sends the PTX grant 756as usual. However, the CM 104 continues to refrain from forwarding mediato the net until a second related timer, the net's wake-up timer 724,expires. Both timers reset when the CM 104 determines that the dormantnet's floor can be granted. The value of the wake-up timer 724 shouldnot be less than the value of the PTX dormancy response timer 728. Afterthe wake-up timer 724 has expired, the CM 104 begins forwarding mediaand media signaling and traffic flow normally. Both timers areconfigurable on a per net basis.

[0196] If the CM 104 determines that it cannot grant the PTT request704, it immediately signals the requesting CD 352 accordingly with a PTXdeny message 708, and the net remains dormant.

[0197] A CD 352 that has entered the Dormant/Idle state 844 may requirea system change, change service options, or experience some otherservice disruption that causes it to never receive and respond to theAYT “wake-up” message 908. The CM 104 maintains a third longer timerthat also resets with the wake-up and PTX dormancy response timers. Thislonger late-riser timer (not shown) is also configurable on a per netbasis. After the late-riser time expires, any CD 352 whose IAH response916 to the AYT wake-up message 908 has not been received is removed fromthe net's list of active participants by the CM 104. Any such removed CD352 to re-registers with the CM 104's SIP server 236 in order to onceagain become a net participant.

[0198] Due to potential delays associated in transitioning a CD 352 outof the Dormant/Idle state 844 to the connected state, both the CD 352and the CM 104 may perform voice buffering to mitigate the transitiondelay perceived by the user.

[0199] Typically, the CD 352 user-interface signals the user, throughvisual or aural mechanisms, at least two milestones in the processing ofa PTT key-press. First, the CD 352 signals that it has detected a PTTkey-press. Later, the CD 352 signals that it has received the CM 104'sPTX message response 868. If the PTX message response 868 grantspermission to broadcast media, the CD 352 user-interface provides anindication that the user may begin talking to the net; otherwise, the CD352 user-interface indicates that the user has been denied permission856 to talk to the net.

[0200] When the net is not dormant, the latency between the transmissionof the PTT request message and receipt of the corresponding PTX responsemessage is relatively small, and the user grows accustomed to beinggranted permission to speak shortly after PTT button is keyed. However,when the net is dormant, a relatively significant delay may separatetransmission of the PTT request 852 and receipt of the corresponding PTXmessage 856 or 868. The delay may occur because the CD 352 may havereleased its traffic channel and experiences a delay in re-establishingpacket data service. The delay may also occur because the CM 104 waitsuntil the net's wake-up timer has expired before sending the PTX messageresponse 856 or 868. In this circumstance, the CD 352 may optimisticallyassume that the CM 104 eventually responds with a PTX grant response 868and signal the user that the PTT request 876 has been granted. To allowthe user to begin speaking “early,” the CD 352 buffers voice internally,until either the PTX request arrives, or it consumes all availableinternal buffer space.

[0201] If the PTX message response arrives and the request is granted,the CD 352 may begin transmitting the (buffered) voice and operationproceeds normally. If the PTX message response arrives and the requestis denied, the CD 352 signals the user that permission to talk to thenet has been denied. Since the user has already started talking, thislate denial may appear to be a priority conflict. Special care is takenin this circumstance to avoid unnecessarily confusing the user. The CM104 signals the PTX deny message 856 as soon as possible to limit thelength of time the user may talk under the assumption that theoutstanding PTT request eventually will be granted.

[0202] If the PTX message does not arrive before all available internalbuffer space is consumed, the CD 352 may simulate a PTX deny message 856and signal the user to stop talking 856. If the CD 352 has not been ableto re-establish service, it may also need to take other error action atthis point and inform the user accordingly. Alternatively, if by thistime, packet data service is re-established, the CD 352 may, in thissituation, begin transmitting voice media to the CM 104 without priorreceipt of a PTX grant message response 868.

[0203] While waiting for the wake-up timer to expire, the CM 104 buffersany voice media received on a net's media channels from the CD 352 thathas sent the outstanding PTT request 852 and eventually sends acorresponding PTX grant response 868. Once the wake-up timer expires,the CM 104 transmits the PTX grant response 868 to the requesting CD352, broadcasts a PTA announcement to the net, and begins broadcastingthe buffered voice media. If the CM 104's internal voice buffer isconsumed before the wake-up timer expires, the CM 104 immediatelytransmits a PTX denial message 856 to the requesting CD 352. Thetreatment of the buffered voice is undefined, but the CM 104 maytransmit the contents of its voice buffer to the net after the wake-uptimer has expired. Once the wake-up timer has expired, net operationproceeds normally.

[0204] The size of the voice media buffer in the CD 352 is chosen basedon the maximum time expected to transition to the IS-707.5 connectedstate 812 from the IS-707.5 dormant/idle state 844. Similarly, the sizeof the media buffer in the CM 104 should be chosen based on the(maximum) value of the net's wake-up timer specified in the CM 104's netdatabase 232.

[0205] A more complete description of the states of the CM 104 follows.The CM 104 implements the NBS Media Signaling state diagram 600 shown inFIG. 15 for each instance of a net. The CM 104 initializes in an idlestate 604 when a net is created. The net remains in the idle state 604as long as no net participant request PTT 608 is granted for control ofthe floor 612 and the net is not dormant 618. The CM 104 resets thehang-time timer 620 to zero upon entering the idle state 604. The CM 104transitions from the idle state 604 to the grant state 612 when a PTTrequest 608 from a net participant is received. The CM 104 transitionsfrom the idle state 604 to the go-dormant state 624 when the hang-timetimer expires.

[0206] The CM 104 transitions from the grant state 612 to the idle state604 and sends a PTX deny 626 response to the requesting CD 352 if thearbitration algorithm denies control of the floor to the requesting CD352. The CM 104 transitions from the grant state 612 to the announcestate 628 and sends a PTX grant response 632 to the requesting CD 352 ifthe arbitration grants control of the floor to the requesting (orinterrupting) CD 352. After sending the PTX grant response 632, the CM104 considers the requesting (or interrupting) CD 352 the net's currenttalker. The CM 104 transitions from the announce state 628 to the talkstate 636 and sends a PTA message 640 announcing the new talker to allnet participants immediately upon entering the announce state 628. Thecurrent talker remains in the talk state 636 as long as no PTT request644 or release message 648 is received from a net participant and thenet's failsafe timer 652 has not expired. The CM 104 resets the net'sfailsafe timer 652 upon entering the talk state 636. While in the talkstate 636, the CM 104 broadcasts media from the net's current talker tothe net.

[0207] The CM 104 transitions from the talk state 636 to the arbitratestate 656 when the PTT request message 644 is received from a netparticipant. The CM 104 transitions from the talk state 636 to therelease-confirm state 660 when the PTT release message 648 is receivedfrom the CD 352 with control of the net's floor. The CM 104 transitionsfrom the talk state 636 to the failsafe-recover state 664 when thefailsafe timer 652 expires. The user is typically given the amount oftime remaining before the failsafe timer expires. The CM 104 broadcastsmedia traffic received from the net's current talker to the net while itremains in the talk state 636. If the net's media buffer is not empty,the CM 104 continues to buffer media received from the net's currenttalker while it broadcasts media traffic to the net.

[0208] The CM 104 enters the arbitrate state 656 as a result ofreceiving the PTT request message 644 while in the talk state 636. TheCD 352 that originated the PTT request message 644 is known as theinterrupting participant. If the interrupting participant and thecurrent talker are identical, the CM 104's PTX grant message 668 waslost and the current talker is re-sending its PTT request 644. The CM104 transitions from the arbitrate state 656 to the talk state 636 andsends the interrupting participant the PTX grant message 668 if theinterrupting participant and the net's current talker are identical. TheCM 104 applies the arbitration algorithm to the net's current talker andthe interrupting participant immediately upon entering the arbitratestate 656 if the interrupting participant and the net's current talkerare distinct.

[0209] The CM 104 transitions from the arbitrate state 656 to the talkstate 636 and sends the interrupting participant a PTX deny message 672if the arbitration algorithm rules in favor of the current talker. TheCM 104 transitions from the arbitrate state 656 to the grant state 612and sends the net's current talker a PTX interrupt message 676 if thearbitration algorithm rules in favor of the interrupting participant.The CM 104 transitions from the release-confirm state 660 to therelease-announce state 680 and sends a PTX confirm message 684 to thecurrent talker immediately upon entering the release-announce state 680.

[0210] The CM 104 transitions from the failsafe-recover state 664 to therelease-announce state 680 and sends a PTX deny message 688 to thecurrent talker immediately upon entering the failsafe-recover state 664.The CM 104 transitions from the release-announce state 680 to the idlestate 604 and sends a PTA release announcement 692 to all netparticipants immediately upon entering the release-announce state 680.The CM 104 transitions from the go-dormant state 624 to the dormantstate 618 and sends a ZZZ message 696 announcing the net has gonedormant to all net participants immediately upon entering the go-dormantstate 624. The net's state machine remains in the dormant state 618 aslong as no net participant requests control of the floor. The CM 104transitions from the dormant state 618 to the wakeup state 706 when aPTT request 704 from a net participant is received.

[0211] The CM 104 transitions from the wakeup state 708 to the dormantstate 618 and sends a PTX deny response 708 to the requesting CD 352 ifthe arbitration algorithm denies control of the floor to the requestingCD 352. Since the net is dormant, this can happen only if the requestingCD 352 has listen-only privileges. The CM 104 transitions from thewakeup state 706 to a wakeup-pending state 712 and sends a AYT wakeuprequest 716 to all net participants if the arbitration grants control ofthe floor to the requesting CD 352. After sending the AYT wakeup request716, the CM 104 considers the requesting CD 352 the net's pendingtalker.

[0212] The CM 104 remains in the wakeup-pending state 712 as long as noPIT request message 720 is received from a net participant, a wake-uptimer 724 has not expired and the a PTX dormancy response timer 728 hasnot expired. The CM 104 resets the wake-up timer 724 and the PTXdormancy response timer 728 upon entering the wakeup-pending state 712.The CM 104 transitions from the wake-up pending state 712 to thedormant-arbitrate state 732 when the PTT request message 720 is receivedfrom a CD 352 distinct from the net's pending talker. The CM 104transitions from the wake-up pending state 712 to a dormant-grant state736 when the net's wake-up timer 724 expires. The CM 104 transitionsfrom the wake-up pending state 712 to a buffered-grant state 740 whenthe PTX dormancy response timer 728 expires.

[0213] The CM 104 applies the arbitration algorithm to the net's pendingtalker and the interrupting participant immediately upon entering thedormant-arbitrate state 732. The CM 104 transitions from thedormant-arbitrate state 732 to the wake-up pending state 712 and sendsthe interrupting participant a PTX deny message 744 if the arbitrationalgorithm rules in favor of the pending talker. The CM 104 transitionsfrom the dormant-arbitrate state 732 to the wake-up pending state 712,sends the pending talker the PTX deny message 744, and considers theinterrupting participant to be the net's new pending talker if thearbitration algorithm rules in favor of the interrupting participant.

[0214] The CM 104 transitions from the dormant-grant state 736 to theannounce state 628 and sends a PTX grant response 748 to the net'spending talker immediately upon entering the dormant-grant state 736.The CM 104 transitions from the buffered-grant state 740 to a bufferingstate 752 and sends a PTX grant response 756 to the net's pending talkerimmediately upon entering the buffered-grant state 740. The net's statemachine remains in the buffering state 752 as long as the wake-up timer724 has not expired. While in the buffering state 752, the CM 104buffers any media traffic received from the net's pending talker.

[0215] The CM 104 transitions from the buffering state 752 to theannounce state 628 when the wake-up timer 724 expires. The CM 104buffers any media traffic received from the net's pending talker in thenet's media buffer while it remains in the buffering state 752. The CM104 responds to any media signaling request that contains invalid orreserved field values by sending an ERR response 760 in an error state764 to the CD 352 that sent the message and otherwise ignore therequest.

[0216] The CD 352 implements the NBS Media Signaling state diagram 800shown in FIG. 16 whenever a user is participating in a net. The CD 352initializes to a startup state 804 after the CD 352 accepts the net'ssession description by sending a SIP ACK message 808 to the CM 104. TheCD 352 transitions from the startup state 804 to a startup-wait state812 and sends a ASK request message 816 to the CM 104 immediately uponentering the startup state 812.

[0217] The CD 352 remains in a listen state 820 as long as the user doesnot press the push-to-talk button 824, no PTA message 828 is receivedfrom the CM 104, and no sleep ZZZ message 832 is received from the CM104. The CD 352 transitions from the listen state 820 to a floor-requeststate 836 when the user presses the push-to-talk button 824. The CD 352transitions from the listen state 820 to a talker-announce state 840when the PTA message 828 is received from the CM 104. The CD 352transitions from the listen state 820 to a dormant-idle state 844 whenthe sleep ZZZ message is 832 received from the CM 104. The CD 352transitions from the floorrequest state 836 to a floor-wait state 848and sends a PTT grant request 852 to the CM 104 immediately uponentering the floor-request state 836.

[0218] The CD 352 remains in the floor-wait state 848 as long as no PTXresponse message 856 is received from the CM 104 and a PTT Abort timer860 has not expired. The CD 352 resets its PTT Abort Timer 860 and a PTTRetransmit Timer (not shown) upon entering the floor-wait state 848. TheCD 352 transitions from the floor-wait state 848 to a talk state 864 andalerts the user that the user has gained control of the net's floor whena PTX grant 868 response message is received from the CM 104. The CD 352transitions from the floor-wait state 848 to a floor-lost state 872 whenthe PTX deny message 856 is received from the CM 104. The CD 352 remainsin the floor-wait state 848 and retransmits an identical PTT request 876to the CM 104 after its PTT Retransmit Timer expires. The CD 352transitions from the floor-wait state 848 to the listen state 820 afterits PTT Abort Timer 860 expires. The CD 352 transitions from the talkstate 864 to a floor-release state 880 if the user releases thepush-to-talk button 884 while still waiting for a PTX response.

[0219] The CD 352 remains in the talk state 864 as long as no PTXinterrupt message 888 is received from the CM 104 and the user has notreleased the push-to-talk button 884. The CD 352 transitions from thetalk state 864 to the floor-lost state 872 when the PTX interruptresponse message 888 is received from the CM 104. The CD 352 transitionsfrom the talk state 864 to the floor-release state 880 when the userreleases the push-to-talk button. The CD 352 remains in the talk state864 when the PTX grant response message 868 is received from the CM 104.The CD 352 transitions from the floor-lost state 872 to the listen state820 and alerts the user 892 with a message indicating that control ofthe net's floor has been lost immediately upon entering the floor-loststate 872.

[0220] The CD 352 transitions from the floor-release state 880 to arelease-wait state 896 and sends a PTT release request 900 to the CM 104immediately upon entering the floor-request state 836. The CD 352remains in the release-wait state 896 as long as no PTX confirm responsemessage 904 is received from the CM 104 and the PTT Abort timer 860 hasnot expired. The CD 352 resets its PTT Abort Timer 860 and a PTTretransmit timer upon entering the release-wait state 896. The PTTretransmit timer is activated each time there is a PTT request orrelease.

[0221] The CD 352 transitions from the release-wait state 896 to thelisten state 820 when the PTX confirm response message 904 is receivedfrom the CM 104. The CD 352 remains in the release-wait state 896 andretransmits an identical PTT release request 900 to the CM 104 after itsPTT Retransmit Timer expires. The CD 352 transitions from therelease-wait state 896 to the listen state 820 after its PTT Abort Timerexpires 860.

[0222] The CD 352 transitions from the talker-announce state 840 to thelisten state 820 and announces the talker immediately upon entering thetalker-announce state 840. The announcement can indicate that a newtalker has control of the floor, the current talker has released thefloor, or that no talker currently has control of the floor.

[0223] The CD 352 remains in the dormant-idle state 844 as long as noAYT request message 908 is received from the CM 104 and the user doesnot press the push-to-talk key 824. The CD 352 transitions from thedormant-idle state 844 to the dormant-wakeup state 912 when the AYTrequest message 908 is received from the CM 104. The CD 352 transitionsfrom the dormant-idle state 844 to the floor-request state 836 when theuser presses the push-to-talk key 824.

[0224] The CD 352 discards any sleep ZZZ message 916 received while inthe dormant-idle state 844. The CD 352 transitions from thedormant-wakeup state 912 to the listen state 820 and sends an IAHresponse message 916 to the CM 104 immediately upon entering thedormant-wakeup state.

[0225] Upon receipt of an AYT ping request 920 received from the CM 104while in any state other than the dormant-idle state 844, the CD 352saves its current state, temporarily transitions to an IAH-reply state924, builds and sends an IAH response message 928 to the CM 104, andreturn to its previous state. The CM 104 sends an ERR response 932 tothe CD 352 when it receives a media signaling error and enters an errorstate 936, such as an malformed request making use of invalid orreserved field values.

[0226] Upon receipt of the ERR response 932 received from the CM 104while in any state, the CD 352 alerts the user that an error hasoccurred, disables the CD 352 (940), and perform any appropriate SIPsignaling to gracefully end its participation in the net 944.

[0227] When the CD 352 has entered one of the dormant state 844, the CD352 may receive point-to-point voice services calls via another IS-707service option, yet remain participants of a dormant net. After thevoice services call is terminated, the CD 352 returns to the IS-707.5dormant/idle state 844.

[0228] However, if the net comes out of the dormant state 844 while theCD 352 has chosen to receive a point-to-point voice service option call,the CD 352 may miss the AYT “wake-up” message request 908 and be removedfrom the list of active participants. In such instances, the CD 352 maydetermine its participant status by sending the CM 104 an ASK request382. Once the CD 352 has been removed from the net's list of activeparticipants, the CD 352 re-registers with the CM 104's SIP server inorder to once again participate in the net.

[0229] The CD 352 allows the user to originate and receive conventionalPSTN point-to-point calls as well as participate in group servicesdiscussions. Although the CD 352 may internally operate in one ofseveral modes, the CD 352 avoids restricting certain functionalitywithin the context of distinct operating modes that the user is requiredto explicitly navigate. Thus, seamless receipt and placement ofpoint-to-point voice-services calls while group services are enabled andactivated.

[0230] The CD 352 may be used to place a point-to-point voice servicesor secure point-to-point packet voice calls at any time, whether groupservices are active or not, as long as the CD 352 is not simultaneouslyacting as a talker. If the CD 352 has registered as a member of a net,the CD 352 unregisters from the net. If the selected point-to-point callis placed via a voice service option, the CD 352 terminates dataservices. Once the point-to-point call has been completed, the CD 352may transparently enable packet data service and reregister as a memberof the current selected net.

[0231] The CD 352 may be used to receive PSTN or secure point-to-pointpacket voice calls while group-services is enabled, within thelimitations imposed by the cellular infrastructure. If the CD 352 joineda net, and the selected net is active, the CD 352 appears busy to anincoming PSTN call and the call is given the appropriate busy treatmentby the cellular infrastructure. If the selected net is quiet but thenet's hang-time 620 has not expired, the call is also given the normalbusy treatment by the cellular infrastructure. However, if the selectednet's hang-time 620 has expired, the net has been placed in dormant mode618, and the CD 352 has released its over-the-air resources, the callmay not be given busy treatment by the infrastructure and the CD 352 maybe paged to initiate receipt of the incoming call.

[0232] While a voice services call is active, the CD 352 is unable toreceive any NBS net traffic. After a voice services call has beencompleted, the CD 352 may be required to rejoin the net as it may havemissed one or more AYT requests 716. Whenever the CD 352 appears busy toan incoming voice services call, the caller is redirected based onwhatever busy treatment has been defined for the called CD 352 (suchcall forwarding, voice mail, etc.) by the cellular infrastructure, asexpected. A user may optionally configure the CD 352 to disable receiptof incoming point-to-point calls while a net is selected and the CD 352is registered as a member.

[0233] The CD 352 also detects if its IP network address has or is aboutto be changed. If the CD 352 is participating in a net when the addresschange occurs, the CD 352 again INVITE itself to the net, as discussedwith respect to FIG. 11.

[0234] For example, a roaming CD 352 may switch cellular systems orcellular networks and thus negotiates a new IP network address. Or, theCD 352 may experience a service disruption or drop the packet dataservice option call for any reason and upon re-establishing service beassigned a new IP network address. If the CD 352 is participating in anet during an address change and does not rejoin the selected net in atimely fashion, the CM 104 eventually expires its membership and removesthe CD 352 from the list for the selected net. The CD 352 is removedfrom the list of active net participants if it does not eventuallyrespond to a series of media signaling AYT request messages 716.

[0235] In the absence of the IS-707.5 Packet Data Service Option, theNBS may operate over the existing and commonly available Quick NetConnect (QNC) packet service. However, QNC does not currently supportdormancy. Accordingly, application level messages such as “go dormant”may be ignored by a CD 352 operating NBS over QNC.

[0236] QNC does provide a protocol stack similar to that provided byIS-707.5. The CD 352 may be configured to negotiate a packet connectionusing QNC rather than IS-707.5, and, if the QNC service is available,treats the connection as a packet data service option connection withoutdormancy or, optionally, CRTP header compression support.

[0237] Under Mobile IP, the CD 352 connects to the network using aforeign agent, which assigns the mobile a care-of address. The care-ofaddress is temporary but legal address to which IP datagrams may beaddressed from anywhere on the Internet. The mobile uses the care-ofaddress to contact its home agent and inform it of the mobile's currentcare-of address. After confirming the identify of the mobile, the homeagent then sends packets addressed to the mobile's permanent homeaddress (which normal Internet routing mechanisms delivers to the homeagent directly or to the home agent's network) to the mobile using themobile's care-of address.

[0238] Although NBS can operate over Mobile IP, Mobile IP maypotentially adversely impact the end-to-end latency and perceived voicequality of NBS media traffic and signaling. This may be in particular ofsignificance if the CD 352 joins a net using its permanent address andthe home agent is located far, in a network topology sense, from the CM104 and the CD 352. In such a case, media traffic may optionally berouted over the public Internet or other variable quality of servicenetworks, which may not have been required if Mobile IP was not used. Toavoid this, it is preferable for the CD 352 to access NBS services usingits care-of address and re-join nets when its care-of address changes.

[0239] Both SIP call signaling and PGP public key encryption use aunique CD 352 user-id or similar unique identifier. The user database232 defines an internal user identifier, which may be forwarded to andused by the CD 352 in media signaling requests. The CD 352 user-idaddress preferably does not contain any private data whose publicdisclosure might compromise the existing cellular infrastructureauthentication mechanisms.

[0240] The CD 352 user address is used in the headers in SIPregistration and invitation, and may be used to form other parts of therequired SIP syntax. The user address is also an input to the generationof the private PGP key used to authenticate SIP requests. The CD 352user-interface allows the user to view the user address. The CD 352user-interface may allow the user to change the user address, at therisk of potentially disrupting the ability to access NBS or satisfy SIPauthentication requests.

[0241] To guard against certain denial of service attacks and prevent CD352 masquerading, the CM 104 may optionally request that the CD 352authenticate itself prior to registering or joining a net. Authorizationis performed at the application level, independent of otherauthorization schemes that may exist at the network or cellularinfrastructure level. CD 352 authorization is also implemented, andoperates, independently of concepts and data structures supportingencrypted (secure) NBS nets.

[0242] In particular, the CM 104 may request that the CD 352 include an“Authorization” header with its SIP requests. The authorization headerallows for the SIP message to be signed by the CD 352 using PGP publickey cryptography signatures.

[0243] Public key cryptography generates a public and private key from aprivate secret key, typically known only to the encryptor (in this case,the CD 352). The private key, in combination with the secret, isrequired to sign a message, but the public key alone can be used toverify a signed message's signature. Thus, to support SIP authorization,each CD 352 is preferably provisioned with a private secret and privatekey, which are never shared. Each CM 104 to which the CD 352 may need toauthorize itself should know the public key of the CD 352. Since thepublic key is not secret, it may be stored as part of the user portionof the database 232 maintained by the CM 104, or accessed throughgeneric public key servers on the Internet.

[0244] The CM 104 may require CD 352 authorization at the server, net,or user level. At the server level, the CM 104 requires all clientsconnecting to the CM 104's SIP server 236 (see FIG. 3) to provideauthorization credentials, rejecting all requests that are notauthorized. When server level authorization is enabled, only clientswhose identities (i.e., a client's public key) are previously known tothe CM 104 may effectively use the server. Server level authorizationcan protect the CM 104 SIP's server 236 from many relatively easydenial-of-service attacks.

[0245] A CM 104 may protect one or more nets it manages throughauthorization, but leave other nets “unprotected.” If the CD 352attempts to INVITE itself to a protected net, the CM 104's SIP server236 rejects the request unless the CD 352 can be authorized by the CM104.

[0246] Also, the CM 104 may use authorization to insure that the CD 352(or any SIP user-agent client in general) does not attempt to masqueradeas another CD 352 and hence either deny service to legitimate netparticipants or passively monitor a net's media channels. If the CM 104requires that a specific CD 352 be authorized, the CM 104 does notaccept any SIP requests from a client connecting as the CD 352 unlessthe client's SIP requests include a PGP signature that may be verifiedby the CM 104. At the user level, authentication may be configured on aper user basis (ie., the CM 104 may require that certain users beauthenticated before while allowing other users to remainunauthenticated).

[0247] The PGP private key may either be administratively provisionedwithin or created by the CD 352, once the CD 352 user address isdefined. The private key need not be stored externally, but theassociated public key is generally loadable into the user portion of thedatabase 232 of any SIP server requiring CD 352 authentication.

[0248] In an embodiment, the primary NBS CD 352 or net participantplatform is a CD 352 MA based cellular handset. Because NBS is builtover IP and IP transport protocols, any IP capable platform withconnectivity to the CM 104 may potentially serve as a NBS CD 352.Accordingly, dial-up users may connect to the CM 104 via the PSTNthrough existing IP terminal-servers operated by Internet ServiceProviders (ISP), as illustrated in FIG. 1. The terminal-server acts as abridge between the PSTN and a LAN supporting IP. The terminal-servercomprises a bank of modems, which provide a connection point forhigh-speed PSTN modems, a server, and one or more network interfaces.The server is capable of hosting multiple independent PPP sessions, onefor each connected modem user. The server also acts as a router, routingIP packets between each of the individual PPP interfaces and any activeLAN interfaces. The CM 104 either includes an integrated (or be deployedin conjunction with an external) commercial off-the-shelfterminal-server.

[0249] The dial-up terminal server supports and includes the ability tonegotiate CRTP Header Compression over its PPP sessions. Similarly, thePPP stack used by a dial-up client also includes and attempts to useCRTP. However, because of the additional bandwidth available overhigh-speed modems, the inability for a dial-up based user to negotiateCRTP Header Compression may not necessarily force a net to avoid usingRTP based payload specifications.

[0250] If the terminal-server is located on a CD 352 MA serviceprovider's internal LAN, and hence near, in a network topology sense, tothe service provider's CM 104, dial-up users may avoidquality-of-service issues that may contribute to high end-to-end latencyif the path between the ISP's terminal-server and the CM 104 traverse aportion of the public Internet. Since PSTN based modems typically do notsupport a dormancy concept similar to that implemented by IS-707.5,dial-up based net participants ignore any sleep messages received fromthe CM 104. Although the user database 232 tracks whether a connectinguser is cellular or land based, this facility is still provided.Accordingly, the CM 104 may or may not send sleep or othermediasignaling messages to dial-up users.

[0251] NBS service areas is designed to be integrated, both to allowusers to roam between service areas as well as to join equivalent netsdefined within separate service areas. Peer-to-peer communicationsbetween multiple CMs 104 takes the form of SIP server redirects, theexchange of user and net database records, and additional messagesspecific to an integrated NBS service.

[0252] In an integrated NBS service embodiment, it may be preferable toallow any CM 104 to assume ownership of a net. Thus, operation of a netis not specific to a particular CM 104 or MCU node 208. The choice of CM104 may be determined dynamically, based on factors such as proximity tothe majority of net participants and available quality of service on aservice providers inter-system network. Similarly, any SIP redirectserver 236 is capable of redirecting any CD 352 to the appropriate MCU'sSIP user-agent server, and/or, if necessary, forwarding the CD 352 toanother SIP redirect server.

[0253] In an integrated NBS service embodiment, a net's net-address hasmeaning throughout the NBS system. As a result, one or more top-levelSIP servers 236 are responsible for redirecting INVITE requests anddistributing net participants to the appropriate MCU nodes 208. Thetop-level SIP servers 236 may share a common user and net database 232,providing similar functionality and redirection decisions at differentnetwork rendezvous points. As a result, the redirection of CD 352originated invitations provides an important and critical layer ofabstraction that allows multiple CM 104 installations to be integratedinto a single homogeneous NBS service.

[0254] In an integrated NBS service, the system scales by duplicatingthe functionality provided by the MCU node manager 256, its associatedset of MCUs 252 (loosely termed an “MCU Cluster”), including its SIPuser-agent server. A single database 232 and administration interface248 is shared by all elements of the system.

[0255] The process by which a CD 352 joins a net in such an integratedsystem is substantially the same as to that used in a system comprisedof a single CM 104 installation. The CD 352 initially sends all SIPrequests to the top-level (now global) SIP redirect server 236. Theredirect server 236 redirects, via SIP mechanisms, the requesting CD 352to the appropriate destination. In the case of an INVITE request to joina net, the destination is the SIP user-agent server 252 associated withthe MCU node 208 with current responsibility for the net in question. Inthe case of an INVITE requesting a current list of nets available to theCD 352, the destination is any user-agent capable of responding to therequest.

[0256] Separately, the redirect server 236 may exchange additionalmessages with the MCU 252 via inter-application messaging usingimplementation-specific protocols and/or messaging conventions. As inthe non-integrated case, special startup action may be necessary toensure that the redirect server 236 may determine a destination forevery legitimate INVITE requests it receives. One embodiment has the SIPregistrations existing at the top-level redirect server 236. Also, thetop-level server may query the system database and attempt to map eachinvitation request to a net definition contained therein.

[0257] The CD 352 may offer encrypted net broadcast communications. Atthe option of net users, voice and data transmitted on a particular netmay be encrypted at the transmitting CD 352, and decrypted by all otherCDs on the net. Encryption is end-to-end, ie., from CD to another. Netcommunications are typically encrypted by a commercial encryptionalgorithm incorporated in a NBS capable CD. The choice of whether a CD352 treats a net as encrypted or unencrypted is at the discretion of thenet users; that is, involvement of the CM 104 is not required.

[0258] Users may select on a net by net basis whether they would prefertraffic transmitted/received on that net to be encrypted/decrypted. Theuser is given the capability to enter an encryption key for the netusing, for example, the phone keypad. The user is thus be capable ofengaging in encrypted communications with other users of the net whohave also selected the encryption option for that net and who are alsousing the same encryption key.

[0259] The user may enable or disable the encryption of net traffic forany net key that the user has entered into the CD 352 at any time. Mediatraffic may be symmetrically encrypted through the use of a symmetrickey (a traffic encryption key, or TEK) that is shared by net users. Nettraffic encryption keys may be generated off-line by a net user or netadministrator and then securely distributed to net participants whomanually enter the keys into their respective communication devices. Thekey is used for media traffic over a particular net, until new keys aregenerated and distributed to the net users to replace the previous netTEK.

[0260] The CD 352 is notified that it is a member of a particular netthrough messages received from the CM 104. The net administrator for aspecific net may set an advisory flag that indicates that the net isintended to be encrypted. This indication is generally advisory, anddoes not necessarily authoritatively indicate that communications on thenet are actually encrypted. The CD 352 user interface allows a user todesignate any net as an encrypted net, and allow the user to input thenet TEK from the CD 352, independently of whether an encrypted advisoryflag for the net has been received by the CM 104.

[0261] The CD 352 may enforce minimum and maximum key lengths. The CD352 may provide a means for a key checksum to be input along with thekey, and if provided, to check the checksum against the key entered. Ifthe checksum is not entered, the CD 352 calculates the checksum andmakes it available for display to the user. The CD 352 does notnecessarily display the key on the CD 352 display after initial keyentry.

[0262] Once a key is successfully entered for a given net, mediatransmissions on the net is encrypted using that particular key, and alltraffic received on the net is decrypted using that particular key. Theencrypted traffic includes additional headers that allow the CD 352 tosynchronize the encryption/decryption process, to allow for latesynchronization (synchronization to a transmission already in progress),and to confirm that the sender and receiver are using identical trafficencryption keys. If a CD 352 receives encrypted traffic (detected by thepresence of the encryption headers) on a net that it has not designatedas encrypted, the CD 352 indicates that it is receiving encryptedtraffic to the user, and does not output traffic (mute the audio orsuppress data output). Similarly, if the CD 352 receives media trafficthat is not encrypted on a net for which it is configured to encrypt, orif the traffic is not decrypted correctly (for instance if the keys areincompatible) the CD 352 alerts the user and mute the traffic.

[0263] The key for an encrypted net may simply be a random (binary)number. In general, the key may be generated by one party in a net, oran administrator for that net, and distributed securely to the netparticipants. Since the key distribution policy is currently left to thenet users, it is a potential source of compromise of the net security.Thus, it is recommended that the net encryption key be distributed usingsecure means, such as PGP encrypted e-mail, to the net participants. Thesecurity manager 20 (FIG. 1) also provides a central repository forcommon net keys. Other methods are also possible, such as a standardtelephone call or face-to-face meeting. Keys may also be distributedautomatically to CDs, using an imbedded PGP secret key into acommunication device for SIP authentication.

[0264] The previous description of the preferred embodiments is providedto enable any person skilled in the art to make or use the presentinvention. The various modifications to these embodiments will bereadily apparent to those skilled in the art, and the generic principlesdefined herein may be applied to other embodiments without the use ofthe inventive faculty.

[0265] Thus, the present invention is not intended to be limited to theembodiments shown herein but is to be accorded the widest scopeconsistent with the principles and novel features disclosed herein.

[0266] Other features and advantages of the invention are set forth inthe following claims.

1. In a controller, a method for maintaining user information in a groupcommunication network, the method comprising: maintaining informationabout a net in the group communication network; and maintaininginformation about a user in the net.
 2. The method of claim 1, whereinthe maintaining information about the net includes maintaining a netidentifier.
 3. The method of claim 1, wherein the maintaininginformation about the net includes maintaining a list of current usersin the net.
 4. The method of claim 1, wherein the maintaininginformation about the net includes maintaining a net status, the netstatus including a secure net or a clear net.
 5. The method of claim 1,wherein the maintaining information about the net includes maintaining anet state, the net state including an active state or a dormant state.6. The method of claim 1, wherein the maintaining information about thenet includes maintaining a net address.
 7. The method of claim 1,wherein the maintaining information about the net includes maintaininginformation identifying an arbitration scheme.
 8. The method of claim 1,wherein the maintaining information about the user includes maintaininga user status, the user status including talking or listening.
 9. Themethod of claim 1, wherein the maintaining information about the userincludes maintaining a user priority.
 10. The method of claim 9, whereinthe user priority includes a user privilege level to modify theinformation about the net.
 11. The method of claim 1, wherein themaintaining information about the user includes maintaining a userInternet protocol (IP) address.
 12. The method of claim 1, wherein themaintaining information about the user includes maintaining informationidentifying existing nets the user is authorized to participate in. 13.In a controller, a database for maintaining user information in a groupcommunication network, the database comprising: a first portion formaintaining information about a net in the group communication network;and a second portion for maintaining information about a user in thenet.
 14. In a controller, a computer-readable medium embodying a methodfor maintaining user information in a group communication network, themethod comprising: maintaining information about a net in the groupcommunication network; and maintaining information about a user in thenet.
 15. The computer-readable medium of claim 14, wherein themaintaining information about the net includes maintaining a netidentifier.
 16. The computer-readable medium of claim 14, wherein themaintaining information about the net includes maintaining a list ofcurrent users in the net.
 17. The computer-readable medium of claim 14,wherein the maintaining information about the net includes maintaining anet status, the net status including a secure net or a clear net. 18.The computer-readable medium of claim 14, wherein the maintaininginformation about the net includes maintaining a net state, the netstate including an active state or a dormant state.
 19. Thecomputer-readable medium of claim 14, wherein the maintaininginformation about the net includes maintaining a net address.
 20. Thecomputer-readable medium of claim 14, wherein the maintaininginformation about the net includes maintaining information identifyingan arbitration scheme.
 21. The computer-readable medium of claim 14,wherein the maintaining information about the user includes maintaininga user status, the user status including talking or listening.
 22. Thecomputer-readable medium of claim 14, wherein the maintaininginformation about the user includes maintaining a user priority.
 23. Thecomputer-readable medium of claim 22, wherein the user priority includesa user privilege level to modify the information about the net.
 24. Thecomputer-readable medium of claim 14, wherein the maintaininginformation about the user includes maintaining a user Internet Protocol(IP) address.
 25. The computer-readable medium of claim 14, wherein themaintaining information about the user includes maintaining informationidentifying existing nets the user is authorized to participate in. 26.A controller for maintaining user information in a group communicationnetwork, the controller comprising: means for maintaining informationabout a net in the group communication network; and means formaintaining information about a user in the net.
 27. The controller ofclaim 26, wherein the means for maintaining information about the netincludes means for maintaining a net identifier.
 28. The controller ofclaim 26, wherein the means for maintaining information about the netincludes means for maintaining a list of current users in the net. 29.The controller of claim 26, wherein the means for maintaininginformation about the net includes means for maintaining a net status,the net status including a secure net or a clear net.
 30. The controllerof claim 26, wherein the means for maintaining information about the netincludes means for maintaining a net state, the net state including anactive state or a dormant state.
 31. The controller of claim 26, whereinthe means for maintaining information about the net includes means formaintaining a net address.
 32. The controller of claim 26, wherein themeans for maintaining information about the net includes means formaintaining information identifying an arbitration scheme.
 33. Thecontroller of claim 26, wherein the means for maintaining informationabout the net includes means for maintaining a user status, the userstatus including talking or listening.
 34. The controller of claim 26,wherein the means for maintaining information about the net includesmeans for maintaining a user priority.
 35. The controller of claim 34,wherein the user priority includes a user privilege level to modify theinformation about the net.
 36. The controller of claim 26, wherein themeans for maintaining information about the net includes means formaintaining a user Internet Protocol (IP) address.
 37. The controller ofclaim 26, wherein the means for maintaining information about the netincludes means for maintaining information identifying existing nets theuser is authorized to participate in.
 38. A controller for maintaininguser information in a group communication network, the controllercomprising: a memory unit; and a processor communicatively coupled tothe memory unit, the processor being capable of: maintaining informationabout a net in the group communication network; and maintaininginformation about a user in the net.
 39. The controller of claim 38,wherein the processor is capable of maintaining a net identifier. 40.The controller of claim 38, wherein the processor is capable ofmaintaining a list of current users in the net.
 41. The controller ofclaim 38, wherein the processor is capable of maintaining a net status,the net status including a secure net or a clear net.
 42. The controllerof claim 38, wherein the processor is capable of maintaining a netstate, the net state including an active state or a dormant state. 43.The controller of claim 38, wherein the processor is capable ofmaintaining a net address.
 44. The controller of claim 38, wherein theprocessor is capable of maintaining information identifying anarbitration scheme.
 45. The controller of claim 38, wherein theprocessor is capable of maintaining a user status, the user statusincluding talking or listening.
 46. The controller of claim 38, whereinthe processor is capable of maintaining a user priority.
 47. Thecontroller of claim 34, wherein the user priority includes a userprivilege level to modify the information about the net.
 48. Thecontroller of claim 38, wherein the processor is capable of maintaininga user Internet Protocol (IP) address.
 49. The controller of claim 38,wherein the processor is capable of maintaining information identifyingexisting nets the user is authorized to participate in.